[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZXCA+4WyI6D+Somy@andrea>
Date: Wed, 6 Dec 2023 15:11:07 +0100
From: Andrea Parri <parri.andrea@...il.com>
To: Palmer Dabbelt <palmer@...belt.com>
Cc: mathieu.desnoyers@...icios.com, paulmck@...nel.org,
Paul Walmsley <paul.walmsley@...ive.com>,
aou@...s.berkeley.edu, mmaas@...gle.com, hboehm@...gle.com,
striker@...ibm.com, charlie@...osinc.com, rehn@...osinc.com,
linux-riscv@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/2] membarrier: riscv: Provide core serializing command
> I see
>
> $ git grep "config MEMBARRIER" fab957c11efe2f405e08b9f0d080524bc2631428
> fab957c11efe2f405e08b9f0d080524bc2631428:init/Kconfig:config MEMBARRIER
>
> so IMO this is just one of those forever bugs. So I'd lean towards
>
> Fixes: fab957c11efe ("RISC-V: Atomic and Locking Code")
Works for me, will apply in v2.
> (or anything in that original patch set). It's not that big of a backport,
> so I think it's safe enough?
Indeed, I think so.
The final version of this fix will likely depend on some machinery/code
introduced by 3ccfebedd8cf54 ("powerpc, membarrier: Skip memory barrier
in switch_mm()"); but, yes, nothing we can't safely adjust I think.
Thanks,
Andrea
Powered by blists - more mailing lists