* [PATCH 1/3] tools: memory-model: Expand definition of barrier
@ 2019-06-20 15:55 Alan Stern
2019-06-20 16:37 ` Paul E. McKenney
0 siblings, 1 reply; 2+ messages in thread
From: Alan Stern @ 2019-06-20 15:55 UTC (permalink / raw)
To: LKMM Maintainers -- Akira Yokosawa, Andrea Parri, Boqun Feng,
Daniel Lustig, David Howells, Jade Alglave, Luc Maranget,
Nicholas Piggin, Paul E. McKenney, Peter Zijlstra, Will Deacon
Cc: Kernel development list
Commit 66be4e66a7f4 ("rcu: locking and unlocking need to always be at
least barriers") added compiler barriers back into rcu_read_lock() and
rcu_read_unlock(). Furthermore, srcu_read_lock() and
srcu_read_unlock() have always contained compiler barriers.
The Linux Kernel Memory Model ought to know about these barriers.
This patch adds them into the memory model.
Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
---
tools/memory-model/linux-kernel.cat | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
Index: usb-devel/tools/memory-model/linux-kernel.cat
===================================================================
--- usb-devel.orig/tools/memory-model/linux-kernel.cat
+++ usb-devel/tools/memory-model/linux-kernel.cat
@@ -47,7 +47,8 @@ let strong-fence = mb | gp
let nonrw-fence = strong-fence | po-rel | acq-po
let fence = nonrw-fence | wmb | rmb
let barrier = fencerel(Barrier | Rmb | Wmb | Mb | Sync-rcu | Sync-srcu |
- Before-atomic | After-atomic | Acquire | Release) |
+ Before-atomic | After-atomic | Acquire | Release |
+ Rcu-lock | Rcu-unlock | Srcu-lock | Srcu-unlock) |
(po ; [Release]) | ([Acquire] ; po)
(**********************************)
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH 1/3] tools: memory-model: Expand definition of barrier
2019-06-20 15:55 [PATCH 1/3] tools: memory-model: Expand definition of barrier Alan Stern
@ 2019-06-20 16:37 ` Paul E. McKenney
0 siblings, 0 replies; 2+ messages in thread
From: Paul E. McKenney @ 2019-06-20 16:37 UTC (permalink / raw)
To: Alan Stern
Cc: LKMM Maintainers -- Akira Yokosawa, Andrea Parri, Boqun Feng,
Daniel Lustig, David Howells, Jade Alglave, Luc Maranget,
Nicholas Piggin, Peter Zijlstra, Will Deacon,
Kernel development list
On Thu, Jun 20, 2019 at 11:55:36AM -0400, Alan Stern wrote:
> Commit 66be4e66a7f4 ("rcu: locking and unlocking need to always be at
> least barriers") added compiler barriers back into rcu_read_lock() and
> rcu_read_unlock(). Furthermore, srcu_read_lock() and
> srcu_read_unlock() have always contained compiler barriers.
>
> The Linux Kernel Memory Model ought to know about these barriers.
> This patch adds them into the memory model.
>
> Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
And yes, much easier to understand this way, thank you!
I have queued them and they both diff equal to your previous patch and
give the expected results on the litmus-tests and github tests having
Result tags.
Thanx, Paul
> ---
>
>
> tools/memory-model/linux-kernel.cat | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> Index: usb-devel/tools/memory-model/linux-kernel.cat
> ===================================================================
> --- usb-devel.orig/tools/memory-model/linux-kernel.cat
> +++ usb-devel/tools/memory-model/linux-kernel.cat
> @@ -47,7 +47,8 @@ let strong-fence = mb | gp
> let nonrw-fence = strong-fence | po-rel | acq-po
> let fence = nonrw-fence | wmb | rmb
> let barrier = fencerel(Barrier | Rmb | Wmb | Mb | Sync-rcu | Sync-srcu |
> - Before-atomic | After-atomic | Acquire | Release) |
> + Before-atomic | After-atomic | Acquire | Release |
> + Rcu-lock | Rcu-unlock | Srcu-lock | Srcu-unlock) |
> (po ; [Release]) | ([Acquire] ; po)
>
> (**********************************)
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2019-06-20 16:38 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-06-20 15:55 [PATCH 1/3] tools: memory-model: Expand definition of barrier Alan Stern
2019-06-20 16:37 ` Paul E. McKenney
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.