mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/herbert/cryptodev-2.6.git
synced 2026-04-18 03:23:53 -04:00
e30d023555
We already use a litmus test in atomic_t.txt to describe atomic RMW + smp_mb__after_atomic() is stronger than acquire (both the read and the write parts are ordered). So make it a litmus test in atomic-tests directory, so that people can access the litmus easily. Additionally, change the processor numbers "P1, P2" to "P0, P1" in atomic_t.txt for the consistency with the processor numbers in the litmus test, which herd can handle. Acked-by: Alan Stern <stern@rowland.harvard.edu> Acked-by: Andrea Parri <parri.andrea@gmail.com> Signed-off-by: Boqun Feng <boqun.feng@gmail.com> Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org> Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
17 lines
660 B
Plaintext
17 lines
660 B
Plaintext
This directory contains litmus tests that are typical to describe the semantics
|
|
of our atomic APIs. For more information about how to "run" a litmus test or
|
|
how to generate a kernel test module based on a litmus test, please see
|
|
tools/memory-model/README.
|
|
|
|
============
|
|
LITMUS TESTS
|
|
============
|
|
|
|
Atomic-RMW+mb__after_atomic-is-stronger-than-acquire
|
|
Test that an atomic RMW followed by a smp_mb__after_atomic() is
|
|
stronger than a normal acquire: both the read and write parts of
|
|
the RMW are ordered before the subsequential memory accesses.
|
|
|
|
Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus
|
|
Test that atomic_set() cannot break the atomicity of atomic RMWs.
|