diff options
| author | Alexei Starovoitov <ast@kernel.org> | 2025-08-25 18:52:17 -0700 |
|---|---|---|
| committer | Alexei Starovoitov <ast@kernel.org> | 2025-08-25 18:52:17 -0700 |
| commit | f4c227cc977f842855ab10de60aa4cd5dd644025 (patch) | |
| tree | a9147dc75a15e4195b18cbf876d6c69aa7d2686f /scripts/lib/kdoc/kdoc_re.py | |
| parent | 4223bf833c8495e40ae2886acbc0ecbe88fa6306 (diff) | |
| parent | 8e4f0b1ebcf2180ab594f204f01279a666dadf3b (diff) | |
Merge branch 'bpf-introduce-and-use-rcu_read_lock_dont_migrate'
Menglong Dong says:
====================
bpf: introduce and use rcu_read_lock_dont_migrate
migrate_disable() and rcu_read_lock() are used to together in many case in
bpf. However, when PREEMPT_RCU is not enabled, rcu_read_lock() will
disable preemption, which indicate migrate_disable(), so we don't need to
call it in this case.
In this series, we introduce rcu_read_lock_dont_migrate and
rcu_read_unlock_migrate, which will call migrate_disable and
migrate_enable only when PREEMPT_RCU enabled. And use
rcu_read_lock_dont_migrate in bpf subsystem.
Changes since V2:
* make rcu_read_lock_dont_migrate() more compatible by using IS_ENABLED()
Changes since V1:
* introduce rcu_read_lock_dont_migrate() instead of
rcu_migrate_disable() + rcu_read_lock()
====================
Link: https://patch.msgid.link/20250821090609.42508-1-dongml2@chinatelecom.cn
Signed-off-by: Alexei Starovoitov <ast@kernel.org>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_re.py')
0 files changed, 0 insertions, 0 deletions
