From: "Paul E. McKenney" <paulmck@kernel.org>
To: Joel Fernandes <joel@joelfernandes.org>
Cc: Boqun Feng <boqun.feng@gmail.com>,
linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Nicholas Piggin <npiggin@gmail.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
Jonathan Corbet <corbet@lwn.net>,
Mauro Carvalho Chehab <mchehab+samsung@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Rob Herring <robh@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
linux-arch@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH v4 0/4] Documentation/litmus-tests: Add litmus tests for atomic APIs
Date: Wed, 1 Apr 2020 09:34:09 -0700 [thread overview]
Message-ID: <20200401163409.GZ19865@paulmck-ThinkPad-P72> (raw)
In-Reply-To: <20200327221843.GA226939@google.com>
On Fri, Mar 27, 2020 at 06:18:43PM -0400, Joel Fernandes wrote:
> On Thu, Mar 26, 2020 at 10:40:18AM +0800, Boqun Feng wrote:
> > A recent discussion raises up the requirement for having test cases for
> > atomic APIs:
> >
> > https://lore.kernel.org/lkml/20200213085849.GL14897@hirez.programming.kicks-ass.net/
> >
> > , and since we already have a way to generate a test module from a
> > litmus test with klitmus[1]. It makes sense that we add more litmus
> > tests for atomic APIs. And based on the previous discussion, I create a
> > new directory Documentation/atomic-tests and put these litmus tests
> > here.
> >
> > This patchset starts the work by adding the litmus tests which are
> > already used in atomic_t.txt, and also improve the atomic_t.txt to make
> > it consistent with the litmus tests.
> >
> > Previous version:
> > v1: https://lore.kernel.org/linux-doc/20200214040132.91934-1-boqun.feng@gmail.com/
> > v2: https://lore.kernel.org/lkml/20200219062627.104736-1-boqun.feng@gmail.com/
> > v3: https://lore.kernel.org/linux-doc/20200227004049.6853-1-boqun.feng@gmail.com/
>
> For full series:
>
> Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
Queued in place of the following commits, with Joel's and Alan's tags
added, thank you all!
Thanx, Paul
c13c55d4 tools/memory-model: Add an exception for limitations on _unless() family
59ffd85 Documentation/locking/atomic: Fix atomic-set litmus test
23c19c8 Documentation/locking/atomic: Introduce atomic-tests directory
3bd201c Documentation/locking/atomic: Add a litmus test for atomic_set()
833f53b Documentation/locking/atomic: Add a litmus test smp_mb__after_atomic()
> One question I had was in the existing atomic_set() documentation, it talks
> about atomic_add_unless() implementation based on locking could have issues.
> It says the way to fix such cases is:
>
> Quote:
> the typical solution is to then implement atomic_set{}() with
> atomic_xchg().
>
> I didn't get how using atomic_xchg() fixes it. Is the assumption there that
> atomic_xchg() would be implemented using locking to avoid atomic_set() having
> issues? If so, we could clarify that in the document.
>
> thanks,
>
> - Joel
>
> >
> > Changes since v3:
> >
> > * Merge two patches on atomic-set litmus test into one as per
> > Alan. (Alan, you have acked only one of the two patches, so I
> > don't add you acked-by for the combined patch).
> >
> > * Move the atomic litmus tests into litmus-tests/atomic to align
> > with Joel's recent patches on RCU litmus tests.
> >
> > I think we still haven't reach to a conclusion for the difference of
> > atomic_add_unless() in herdtools, and I'm currently reading the source
> > code of herd to resovle this. This is just an updated version to resolve
> > ealier comments and react on Joel's RCU litmus tests.
> >
> > Regards,
> > Boqun
> >
> > [1]: http://diy.inria.fr/doc/litmus.html#klitmus
> >
> > 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()
> >
> > Documentation/atomic_t.txt | 24 +++++++-------
> > ...ter_atomic-is-stronger-than-acquire.litmus | 32 +++++++++++++++++++
> > ...c-RMW-ops-are-atomic-WRT-atomic_set.litmus | 24 ++++++++++++++
> > Documentation/litmus-tests/atomic/README | 16 ++++++++++
> > tools/memory-model/README | 10 ++++--
> > 5 files changed, 91 insertions(+), 15 deletions(-)
> > 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/atomic/README
> >
> > --
> > 2.25.1
> >
prev parent reply other threads:[~2020-04-01 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-26 2:40 [PATCH v4 0/4] Documentation/litmus-tests: Add litmus tests for atomic APIs Boqun Feng
2020-03-26 2:40 ` [PATCH v4 1/4] tools/memory-model: Add an exception for limitations on _unless() family Boqun Feng
2020-03-26 2:40 ` [PATCH v4 2/4] Documentation/litmus-tests: Introduce atomic directory Boqun Feng
2020-03-26 2:40 ` [PATCH v4 3/4] Documentation/litmus-tests/atomic: Add a test for atomic_set() Boqun Feng
2020-03-26 14:23 ` Alan Stern
2020-03-26 2:40 ` [PATCH v4 4/4] Documentation/litmus-tests/atomic: Add a test for smp_mb__after_atomic() Boqun Feng
2020-03-27 22:18 ` [PATCH v4 0/4] Documentation/litmus-tests: Add litmus tests for atomic APIs Joel Fernandes
2020-03-31 1:40 ` Boqun Feng
2020-04-02 3:58 ` Joel Fernandes
2020-04-02 8:03 ` Boqun Feng
2020-04-04 19:57 ` Joel Fernandes
2020-04-01 16:34 ` Paul E. McKenney [this message]
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=20200401163409.GZ19865@paulmck-ThinkPad-P72 \
--to=paulmck@kernel.org \
--cc=Jonathan.Cameron@huawei.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=mchehab+samsung@kernel.org \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=peterz@infradead.org \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--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).