forked from kernel-patches/bpf
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
tools/memory-model: Provide extra ordering for unlock+lock pair on th…
…e same CPU A recent discussion[1] shows that we are in favor of strengthening the ordering of unlock + lock on the same CPU: a unlock and a po-after lock should provide the so-called RCtso ordering, that is a memory access S po-before the unlock should be ordered against a memory access R po-after the lock, unless S is a store and R is a load. The strengthening meets programmers' expection that "sequence of two locked regions to be ordered wrt each other" (from Linus), and can reduce the mental burden when using locks. Therefore add it in LKMM. [1]: https://lore.kernel.org/lkml/[email protected]/ Co-developed-by: Alan Stern <[email protected]> Signed-off-by: Alan Stern <[email protected]> Signed-off-by: Boqun Feng <[email protected]> Reviewed-by: Michael Ellerman <[email protected]> (powerpc) Acked-by: Palmer Dabbelt <[email protected]> (RISC-V) Acked-by: Peter Zijlstra (Intel) <[email protected]> Signed-off-by: Paul E. McKenney <[email protected]>
- x86_vmware_for_v6.0_rc1
- x86_vdso_for_v5.19_rc1
- x86_urgent_for_v5.19
- x86_urgent_for_v5.19_rc8
- x86_urgent_for_v5.19_rc7
- x86_urgent_for_v5.19_rc6
- x86_urgent_for_v5.18_rc5
- x86_urgent_for_v5.18_rc2
- x86_urgent_for_v5.17_rc8
- x86_urgent_for_v5.17_rc5
- x86_urgent_for_v5.17_rc4
- x86_urgent_for_v5.17_rc2
- x86_tdx_for_v5.19_rc1
- x86_splitlock_for_v5.19_rc1
- x86_sgx_for_v5.18_rc1
- x86_sev_for_v5.19_rc1
- x86_sev_for_v5.18_rc1
- x86_platform_for_v5.19_rc1
- x86_paravirt_for_v5.18_rc1
- x86_mm_for_v6.0_rc1
- x86_mm_for_v5.19_rc1
- x86_misc_for_v6.0_rc1
- x86_misc_for_v5.19_rc1
- x86_misc_for_v5.18_rc1
- x86_microcode_for_v5.19_rc1
- x86_kdump_for_v6.0_rc1
- x86_kdump_for_v5.19_rc1
- x86_fpu_for_v6.0_rc1
- x86_fpu_for_v5.19_rc1
- x86_cpu_for_v6.0_rc1
- x86_cpu_for_v5.19_rc1
- x86_cpu_for_v5.18_rc1
- x86_core_for_5.18_rc1
- x86_core_for_v6.0_rc1
- x86_core_for_v5.19_rc1
- x86_cleanups_for_v6.0_rc1
- x86_cleanups_for_v5.19_rc1
- x86_cleanups_for_v5.18_rc1
- x86_cc_for_v5.18_rc1
- x86_build_for_v6.0_rc1
- x86_build_for_v5.19_rc1
- x86_build_for_v5.18_rc1
- x86_asm_for_v5.19_rc1
- x86_apic_for_v5.19_rc1
- x86-urgent-2022-06-19
- x86-urgent-2022-06-05
- x86-urgent-2022-05-15
- x86-urgent-2022-05-08
- x86-urgent-2022-04-17
- x86-urgent-2022-04-03
- x86-pasid-2022-03-21
- x86-mm-2022-06-05
- x86-microcode-2022-06-05
- x86-irq-2022-05-23
- x86-cleanups-2022-06-05
- x86-boot-2022-06-05
- v6.2-rc2
- v6.2-rc1
- v6.1
- v6.1-rc8
- v6.1-rc7
- v6.1-rc6
- v6.1-rc5
- v6.1-rc4
- v6.1-rc3
- v6.1-rc2
- v6.1-rc1
- v6.0
- v6.0-rc7
- v6.0-rc6
- v6.0-rc5
- v6.0-rc4
- v6.0-rc3
- v6.0-rc2
- v6.0-rc1
- v5.19
- v5.19-rc8
- v5.19-rc7
- v5.19-rc6
- v5.19-rc5
- v5.19-rc4
- v5.19-rc3
- v5.19-rc2
- v5.19-rc1
- v5.18
- v5.18-rc7
- v5.18-rc6
- v5.18-rc5
- v5.18-rc4
- v5.18-rc3
- v5.18-rc2
- v5.18-rc1
- v5.17
- v5.17-rc8
- v5.17-rc7
- v5.17-rc6
- v5.17-rc5
- v5.17-rc4
- v5.17-rc3
- v5.17-rc2
- v5.17-rc1
- timers-urgent-2022-05-08
- timers-urgent-2022-04-17
- timers-core-2022-08-01
- timers-core-2022-06-05
- timers-core-2022-05-23
- timers-core-2022-03-21
- tai-for-tracing
- smp-urgent-2022-04-17
- smp-core-2022-05-23
- sched-urgent-2022-06-19
- sched-urgent-2022-06-05
- sched-urgent-2022-05-15
- sched-core-2022-08-01
- sched-core-2022-05-23
- sched-core-2022-03-22
- sched-core-2022-03-21
- sched_urgent_for_v5.19_rc8
- sched_urgent_for_v5.18_rc4
- sched_urgent_for_v5.18_rc2
- sched_urgent_for_v5.17_rc5
- sched_urgent_for_v5.17_rc4
- sched_urgent_for_v5.17_rc2
- sched_urgent_for_v5.17_rc2_p2
- ras_core_for_v6.0_rc1
- ras_core_for_v5.19_rc1
- ras_core_for_v5.18_rc1
- perf-urgent-2022-06-05
- perf-core-2022-08-01
- perf-core-2022-06-05
- perf-core-2022-05-23
- perf-core-2022-03-21
- perf_urgent_for_v5.19_rc8
- perf_urgent_for_v5.19_rc7
- perf_urgent_for_v5.18_rc4
- perf_urgent_for_v5.18_rc2
- perf_urgent_for_v5.17_rc4
- perf_urgent_for_v5.17_rc3
- perf_urgent_for_v5.17_rc2
- perf_urgent_for_v5.17_rc2_p2
- objtool-urgent-2022-06-19
- objtool-urgent-2022-06-05
- objtool-core-2022-05-23
- objtool_urgent_for_v5.18_rc5
- objtool_urgent_for_v5.17_rc4
- objtool_urgent_for_v5.17_rc3
- locking-urgent-2022-06-19
- locking-urgent-2022-05-08
- locking-core-2022-08-01
- locking-core-2022-05-23
- locking-core-2022-03-21
- locking_urgent_for_v5.19
- locking_urgent_for_v5.18_rc2
- locking_urgent_for_v5.17_rc5
- irq-urgent-2022-06-19
- irq-urgent-2022-05-15
- irq-urgent-2022-05-08
- irq-urgent-2022-04-17
- irq-urgent-2022-04-10
- irq-urgent-2022-02-27
- irq-urgent-2022-02-13
- irq-core-2022-08-01
- irq-core-2022-05-23
- irq-core-2022-03-21
- irq-api-2022-02-21
- irq_urgent_for_v5.19_rc6
- irq_urgent_for_v5.18_rc5
- irq_urgent_for_v5.17_rc3
- irq_urgent_for_v5.17_rc2
- irq_urgent_for_v5.17_rc2_p2
- for-netdev
- core-urgent-2022-05-08
- core-urgent-2022-04-03
- core-debugobjects-2022-05-23
- core-core-2022-05-23
- core-core-2022-03-21
1 parent
fa55b7d
commit ddfe129
Showing
2 changed files
with
28 additions
and
22 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters