diff options
author | Rob Clark <[email protected]> | 2023-03-20 07:43:42 -0700 |
---|---|---|
committer | Bjorn Andersson <[email protected]> | 2023-04-06 11:42:23 -0700 |
commit | 5808c532ca0a983d643319caca44f2bcb148298f (patch) | |
tree | c98f4012e2c168371527d7fef62d2037f7c739cf /lib/test_fortify/write_overflow-strncpy-src.c | |
parent | c78ad8597ed961e822bf86ce7f1916dbfba255ef (diff) |
soc: qcom: smd-rpm: Use GFP_ATOMIC in write path
Preparing for better lockdep annotations for things that happen in runpm
suspend/resume path vs shrinker/reclaim in the following patches, we
need to avoid allocations that can trigger reclaim in the icc_set_bw()
path. In the RPMh case, rpmh_write_batch() already uses GFP_ATOMIC, so
it should be reasonable to use in the smd-rpm case as well.
Alternatively, 256bytes is small enough for a function that isn't called
recursively to allocate on-stack.
Signed-off-by: Rob Clark <[email protected]>
Signed-off-by: Bjorn Andersson <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'lib/test_fortify/write_overflow-strncpy-src.c')
0 files changed, 0 insertions, 0 deletions