[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ceaa37af-407f-4612-807a-6a6c5a1edda5@rowland.harvard.edu>
Date: Tue, 21 Mar 2023 21:13:23 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Andrea Parri <parri.andrea@...il.com>
Cc: "Paul E. McKenney" <paulmck@...nel.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
kernel-team@...a.com, mingo@...nel.org, will@...nel.org,
peterz@...radead.org, boqun.feng@...il.com, npiggin@...il.com,
dhowells@...hat.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
akiyks@...il.com,
Jonas Oberhauser <jonas.oberhauser@...weicloud.com>
Subject: Re: [PATCH memory-model 5/8] tools/memory-model: Provide exact SRCU
semantics
On Wed, Mar 22, 2023 at 02:07:40AM +0100, Andrea Parri wrote:
> > +let carry-srcu-data = (data ; [~ Srcu-unlock] ; rf)*
>
> > +let carry-dep = (data ; [~ Srcu-unlock] ; rfi)*
>
> Nit: we use "~M" (no space after the unary operator) in this file, is
> there a reason for the different styles?
No reason that I know of, just lack of thought (as far as
carry-srcu-data is concerned). Feel free to change it.
Alan
Powered by blists - more mailing lists