From: Andrea Parri <andrea.parri@amarulasolutions.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "Paul E. McKenney" <paulmck@linux.ibm.com>,
LKMM Maintainers -- Akira Yokosawa <akiyks@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Nicholas Piggin <npiggin@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will.deacon@arm.com>,
Kernel development list <linux-kernel@vger.kernel.org>,
Joel Fernandes <joel@joelfernandes.org>
Subject: Re: [PATCH 3/3] tools: memory-model: Add data-race detection
Date: Fri, 26 Apr 2019 16:41:08 +0200 [thread overview]
Message-ID: <20190426144108.GA6235@andrea> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1904221214370.1384-100000@iolanthe.rowland.org>
On Mon, Apr 22, 2019 at 12:18:09PM -0400, Alan Stern wrote:
> This patch adds data-race detection to the Linux-Kernel Memory Model.
> As part of this effort, support is added for:
>
> compiler barriers (the barrier() function), and
>
> a new Preserved Program Order term: (addr ; [Plain] ; wmb)
>
> Data races are marked with a special Flag warning in herd. It is
> not guaranteed that the model will provide accurate predictions when a
> data race is present.
>
> The patch does not include documentation for the data-race detection
> facility. The basic design has been explained in various emails, and
> a separate documentation patch will be submitted later.
>
> This work is based on an earlier formulation of data races for the
> LKMM by Andrea Parri.
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
For the entire series,
Reviewed-by: Andrea Parri <andrea.parri@amarulasolutions.com>
Thanks,
Andrea
next prev parent reply other threads:[~2019-04-26 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 16:18 [PATCH 3/3] tools: memory-model: Add data-race detection Alan Stern
2019-04-26 14:41 ` Andrea Parri [this message]
2019-04-28 22:28 ` Paul E. McKenney
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=20190426144108.GA6235@andrea \
--to=andrea.parri@amarulasolutions.com \
--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-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=paulmck@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.com \
/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