[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f93f140b-13bc-4d00-adee-46cc1c016480@rowland.harvard.edu>
Date: Fri, 7 Jun 2024 21:00:07 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Jonas Oberhauser <jonas.oberhauser@...weicloud.com>
Cc: paulmck@...nel.org, parri.andrea@...il.com, 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, dlustig@...dia.com, joel@...lfernandes.org,
urezki@...il.com, quic_neeraju@...cinc.com, frederic@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCHv2 0/4] tools/memory-model: Define more of LKMM in
tools/memory-model
On Wed, Jun 05, 2024 at 09:58:42PM +0200, Jonas Oberhauser wrote:
>
>
> Am 6/4/2024 um 7:56 PM schrieb Alan Stern:
> > Just to clarify: Your first step encompasses patches 1 - 3, and the
> > second step is patch 4. The first three patches can be applied now, but
> > the last one needs to wait until herd7 has been updated. Is this all
> > correct?
>
> Exactly.
With regard to patch 4, how much thought have you and Hernan given to
backward compatibility? Once herd7 is changed, old memory model files
will no longer work correctly.
To avoid being so disruptive, perhaps the changes to herd7 should be
under control of a new command-line or config-file switch. If the
switch is enabled, the new simplified code gets used; otherwise herd7
would continue to use its old built-in rules for special tags.
Alan
Powered by blists - more mailing lists