From: "Paul E. McKenney" <paulmck@kernel.org>
To: torvalds@linux-foundation.org
Cc: parav@nvidia.com, will@kernel.org, stern@rowland.harvard.edu,
kushagra765@outlook.com, jonas.oberhauser@huawei.com,
linux-kernel@vger.kernel.org, kernel-team@meta.com
Subject: [GIT PULL] LKMM changes for v6.3
Date: Tue, 21 Feb 2023 17:56:59 -0800 [thread overview]
Message-ID: <20230222015659.GA1344672@paulmck-ThinkPad-P17-Gen-1> (raw)
Hello, Linus,
Please pull the latest LKMM changes from:
git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git tags/lkmm.2023.02.15a
# HEAD: 9ba7d3b3b826ef47c1b7b8dbc2d57da868168128: tools: memory-model: Make plain accesses carry dependencies (2023-01-03 20:47:04 -0800)
----------------------------------------------------------------
LKMM updates for v6.3
Documentation updates.
Add read-modify-write sequences, which means that stronger primitives
more consistently result in stronger ordering, while still remaining in
the envelope of the hardware that supports Linux.
Address, data, and control dependencies used to ignore data that was
stored in temporaries. This update extends these dependency chains to
include unmarked intra-thread stores and loads. Note that these unmarked
stores and loads should not be concurrently accessed from multiple
threads, and doing so will cause LKMM to flag such accesses as data races.
----------------------------------------------------------------
Alan Stern (1):
tools: memory-model: Add rmw-sequences to the LKMM
Jonas Oberhauser (1):
tools: memory-model: Make plain accesses carry dependencies
Kushagra Verma (1):
Documentation: Fixed a typo in atomic_t.txt
Parav Pandit (1):
locking/memory-barriers.txt: Improve documentation for writel() example
Documentation/atomic_t.txt | 2 +-
Documentation/memory-barriers.txt | 22 ++++++-------
tools/memory-model/Documentation/explanation.txt | 39 +++++++++++++++++++++++-
tools/memory-model/linux-kernel.bell | 6 ++++
tools/memory-model/linux-kernel.cat | 5 +--
tools/memory-model/litmus-tests/dep+plain.litmus | 31 +++++++++++++++++++
6 files changed, 90 insertions(+), 15 deletions(-)
create mode 100644 tools/memory-model/litmus-tests/dep+plain.litmus
next reply other threads:[~2023-02-22 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 1:56 Paul E. McKenney [this message]
2023-02-23 18:47 ` 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=20230222015659.GA1344672@paulmck-ThinkPad-P17-Gen-1 \
--to=paulmck@kernel.org \
--cc=jonas.oberhauser@huawei.com \
--cc=kernel-team@meta.com \
--cc=kushagra765@outlook.com \
--cc=linux-kernel@vger.kernel.org \
--cc=parav@nvidia.com \
--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
all inboxes | Powered by JetHome®