[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <357b3147-22e0-4081-a9ac-524b65251d62@rowland.harvard.edu>
Date: Mon, 16 Jun 2025 10:11:10 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Andrea Parri <parri.andrea@...il.com>
Cc: Thomas Haas <t.haas@...bs.de>, Peter Zijlstra <peterz@...radead.org>,
Will Deacon <will@...nel.org>, Boqun Feng <boqun.feng@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
David Howells <dhowells@...hat.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
"Paul E. McKenney" <paulmck@...nel.org>,
Akira Yokosawa <akiyks@...il.com>,
Daniel Lustig <dlustig@...dia.com>,
Joel Fernandes <joelagnelf@...dia.com>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
lkmm@...ts.linux.dev, hernan.poncedeleon@...weicloud.com,
jonas.oberhauser@...weicloud.com,
"r.maseli@...bs.de" <r.maseli@...bs.de>
Subject: Re: [RFC] Potential problem in qspinlock due to mixed-size accesses
On Mon, Jun 16, 2025 at 08:21:50AM +0200, Andrea Parri wrote:
> > Thanks for the praise. I expected more questioning/discussion and less
> > immediate acceptance :)
>
> Well, the discussion isn't closed yet. ;-)
>
>
> > Maybe one should also take into consideration a hypothetical extension of
> > LKMM to MSA.
> > I think LKMM (and also C11) do not preserve REL->ACQ ordering because this
> > would disallow their implementation as simple stores/loads on TSO.
> > That being said, maybe preserving "rmw;[REL];po;[ACQ]" on the
> > language-level would be fine and sufficient for qspinlock.
>
> On PPC say, the expression can translate to a sequence "lwsync ; lwarx ;
> stwcx. ; ... ; lwz ; lwsync", in which the order of the two loads is not
> necessarily preserved.
>
> MSAs have been on the LKMM TODO list for quite some time. I'm confident
> this thread will help to make some progress or at least to reinforce the
> interest in the topic.
Indeed. I was surprised to learn that CPUs can sometimes change a
32-bit load into two 16-bit loads.
My question is: Do we have enough general knowledge at this point about
how the various types of hardware handle mixed-size accesses to come up
with a memory model everyone can agree one?
Alan
Powered by blists - more mailing lists