linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	stern@rowland.harvard.edu, parri.andrea@gmail.com,
	will@kernel.org, peterz@infradead.org, boqun.feng@gmail.com,
	npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
	luc.maranget@inria.fr, akiyks@gmail.com, dlustig@nvidia.com,
	joel@joelfernandes.org, mark.rutland@arm.com
Subject: [GIT PULL] LKMM changes for v6.10
Date: Sun, 12 May 2024 10:41:44 -0700	[thread overview]
Message-ID: <9a2178f8-a33a-4b0e-a867-30ea44761e8a@paulmck-laptop> (raw)

Hello, Linux,

When the merge window opens, please pull this LKMM update from:

  git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/lkmm.2024.05.10a
  HEAD: 2ba5b4130e3d5d05c95981e1d2e660d57e613fda: Documentation/litmus-tests: Make cmpxchg() tests safe for klitmus (2024-05-06 14:29:21 -0700)

----------------------------------------------------------------
lkmm: Upgrade LKMM documentation

This commit upgrades LKMM documentation, perhaps most notably adding
a number of litmus tests illustrating cmpxchg() ordering properties.
TL;DR: Failing cmpxchg() operations provide no ordering.

----------------------------------------------------------------
Paul E. McKenney (4):
      Documentation/litmus-tests: Add locking tests to README
      Documentation/litmus-tests: Demonstrate unordered failing cmpxchg
      Documentation/atomic_t: Emphasize that failed atomic operations give no ordering
      Documentation/litmus-tests: Make cmpxchg() tests safe for klitmus

 Documentation/atomic_t.txt                         |  4 +-
 Documentation/litmus-tests/README                  | 45 ++++++++++++++++++++++
 .../atomic/cmpxchg-fail-ordered-1.litmus           | 35 +++++++++++++++++
 .../atomic/cmpxchg-fail-ordered-2.litmus           | 30 +++++++++++++++
 .../atomic/cmpxchg-fail-unordered-1.litmus         | 34 ++++++++++++++++
 .../atomic/cmpxchg-fail-unordered-2.litmus         | 30 +++++++++++++++
 6 files changed, 176 insertions(+), 2 deletions(-)
 create mode 100644 Documentation/litmus-tests/atomic/cmpxchg-fail-ordered-1.litmus
 create mode 100644 Documentation/litmus-tests/atomic/cmpxchg-fail-ordered-2.litmus
 create mode 100644 Documentation/litmus-tests/atomic/cmpxchg-fail-unordered-1.litmus
 create mode 100644 Documentation/litmus-tests/atomic/cmpxchg-fail-unordered-2.litmus

             reply	other threads:[~2024-05-12 17:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-12 17:41 Paul E. McKenney [this message]
2024-05-13 17:27 ` [GIT PULL] LKMM changes for v6.10 pr-tracker-bot

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=9a2178f8-a33a-4b0e-a867-30ea44761e8a@paulmck-laptop \
    --to=paulmck@kernel.org \
    --cc=akiyks@gmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=mark.rutland@arm.com \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=peterz@infradead.org \
    --cc=stern@rowland.harvard.edu \
    --cc=torvalds@linux-foundation.org \
    --cc=will@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).