[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Zk8GkFlnKeyIgYQb@andrea>
Date: Thu, 23 May 2024 11:04:16 +0200
From: Andrea Parri <parri.andrea@...il.com>
To: Hernan Ponce de Leon <hernan.poncedeleon@...weicloud.com>
Cc: Alan Stern <stern@...land.harvard.edu>,
Jonas Oberhauser <jonas.oberhauser@...weicloud.com>,
"Paul E. McKenney" <paulmck@...nel.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
kernel-team@...a.com, boqun.feng@...il.com, j.alglave@....ac.uk,
luc.maranget@...ia.fr, Joel Fernandes <joel@...lfernandes.org>
Subject: Re: LKMM: Making RMW barriers explicit
> It would be much simpler if
> one could find all the information to support lkmm in tools/memory-model/
> (in the form of the model + some comments or a .txt to cover those things we
> cannot move out of the tool implementation), rather than having to dive into
> herd7 code.
Got it. And I do find that very relatable to LKMM developers who, like me,
are definitely not fluent in OCaml. :-/
Let me draft some .txt to such effect, based on but expanding and hopefully
completing my previous remarks in
https://lore.kernel.org/lkml/ZjrSm119+IfIU9eU@andrea/
Having something like that "on paper" can also help evaluate future changes
to the tool and/or model.
Thank you for the suggestion.
Andrea
Powered by blists - more mailing lists