[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230710093751.GC32673@willie-the-truck>
Date: Mon, 10 Jul 2023 10:37:52 +0100
From: Will Deacon <will@...nel.org>
To: Maria Yu <quic_aiquny@...cinc.com>
Cc: corbet@....net, catalin.marinas@....com, maz@...nel.org,
quic_pkondeti@...cinc.com, quic_kaushalk@...cinc.com,
quic_satyap@...cinc.com, quic_shashim@...cinc.com,
quic_songxue@...cinc.com, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] arm64: Add the arm64.nolse_atomics command line option
On Mon, Jul 10, 2023 at 01:59:55PM +0800, Maria Yu wrote:
> In order to be able to disable lse_atomic even if cpu
> support it, most likely because of memory controller
> cannot deal with the lse atomic instructions, use a
> new idreg override to deal with it.
This should not be a problem for cacheable memory though, right?
Given that Linux does not issue atomic operations to non-cacheable mappings,
I'm struggling to see why there's a problem here.
Please can you explain the problem that you are trying to solve?
Will
Powered by blists - more mailing lists