From: "Paul E. McKenney" <paulmck@kernel.org>
To: mingo@kernel.org
Cc: linux-kernel@vger.kernel.org, akiyks@gmail.com,
boqun.feng@gmail.com, elver@google.com, joel@joelfernandes.org,
tglx@linutronix.de
Subject: [GIT PULL memory-model] LKMM commits for v5.9
Date: Tue, 14 Jul 2020 10:43:23 -0700 [thread overview]
Message-ID: <20200714174323.GA32508@paulmck-ThinkPad-P72> (raw)
Hello, Ingo!
This pull request contains Linux-Kernel Memory-Model commits for v5.9.
These have been subjected to LKML review:
https://lore.kernel.org/lkml/20200623005152.GA27459@paulmck-ThinkPad-P72/
All of these have also been subjected to the kbuild test robot and
-next testing. The following changes since v5.8-rc3 are available in
the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git lkmm
for you to fetch changes up to 5ef0a07a7928539d46fdb163acfad28c6d877a89:
Documentation/litmus-tests: Add note on herd7 7.56 in atomic litmus test (2020-06-29 12:05:18 -0700)
----------------------------------------------------------------
Akira Yokosawa (5):
tools/memory-model: Fix reference to litmus test in recipes.txt
Documentation/litmus-tests: Merge atomic's README into top-level one
tools/memory-model/README: Expand dependency of klitmus7
tools/memory-model/README: Mention herdtools7 7.56 in compatibility table
Documentation/litmus-tests: Add note on herd7 7.56 in atomic litmus test
Boqun Feng (4):
tools/memory-model: Add an exception for limitations on _unless() family
Documentation/litmus-tests: Introduce atomic directory
Documentation/litmus-tests/atomic: Add a test for atomic_set()
Documentation/litmus-tests/atomic: Add a test for smp_mb__after_atomic()
Joel Fernandes (Google) (4):
Documentation: LKMM: Add litmus test for RCU GP guarantee where updater frees object
Documentation: LKMM: Add litmus test for RCU GP guarantee where reader stores
MAINTAINERS: Update maintainers for new Documentation/litmus-tests
Documentation/litmus-tests: Cite an RCU litmus test
Marco Elver (1):
tools/memory-model: Fix "conflict" definition
Paul E. McKenney (1):
tools/memory-model: Add recent references
Documentation/atomic_t.txt | 24 +++----
Documentation/litmus-tests/README | 35 +++++++++
...b__after_atomic-is-stronger-than-acquire.litmus | 32 +++++++++
...Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus | 25 +++++++
.../litmus-tests/rcu/RCU+sync+free.litmus | 42 +++++++++++
.../litmus-tests/rcu/RCU+sync+read.litmus | 37 ++++++++++
MAINTAINERS | 2 +
tools/memory-model/Documentation/explanation.txt | 83 ++++++++++++----------
tools/memory-model/Documentation/recipes.txt | 2 +-
tools/memory-model/Documentation/references.txt | 21 +++++-
tools/memory-model/README | 40 +++++++++--
11 files changed, 285 insertions(+), 58 deletions(-)
create mode 100644 Documentation/litmus-tests/README
create mode 100644 Documentation/litmus-tests/atomic/Atomic-RMW+mb__after_atomic-is-stronger-than-acquire.litmus
create mode 100644 Documentation/litmus-tests/atomic/Atomic-RMW-ops-are-atomic-WRT-atomic_set.litmus
create mode 100644 Documentation/litmus-tests/rcu/RCU+sync+free.litmus
create mode 100644 Documentation/litmus-tests/rcu/RCU+sync+read.litmus
reply other threads:[~2020-07-14 17:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200714174323.GA32508@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=elver@google.com \
--cc=joel@joelfernandes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®