diff options
author | 2025-01-08 09:07:17 +0800 | |
---|---|---|
committer | 2025-01-08 18:06:36 -0800 | |
commit | 9e6c958b546692fcdd0da2c2c3b2ac1da6e0233f (patch) | |
tree | 9908aa51aa64a15b32c570057823084f2e57d74c /tools/perf/scripts/python/export-to-postgresql.py | |
parent | bpf: Remove migrate_{disable|enable} from bpf_cgrp_storage_lock helpers (diff) | |
download | linux-rng-9e6c958b546692fcdd0da2c2c3b2ac1da6e0233f.tar.xz linux-rng-9e6c958b546692fcdd0da2c2c3b2ac1da6e0233f.zip |
bpf: Remove migrate_{disable|enable} from bpf_task_storage_lock helpers
Three callers of bpf_task_storage_lock() are ->map_lookup_elem,
->map_update_elem, ->map_delete_elem from bpf syscall. BPF syscall for
these three operations of task storage has already disabled migration.
Another two callers are bpf_task_storage_get() and
bpf_task_storage_delete() helpers which will be used by BPF program.
Two callers of bpf_task_storage_trylock() are bpf_task_storage_get() and
bpf_task_storage_delete() helpers. The running contexts of these helpers
have already disabled migration.
Therefore, it is safe to remove migrate_{disable|enable} from task
storage lock helpers for these call sites. However,
bpf_task_storage_free() also invokes bpf_task_storage_lock() and its
running context doesn't disable migration, therefore, add the missed
migrate_{disable|enable} in bpf_task_storage_free().
Signed-off-by: Hou Tao <houtao1@huawei.com>
Link: https://lore.kernel.org/r/20250108010728.207536-6-houtao@huaweicloud.com
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions