[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240823135459.GA28487@lst.de>
Date: Fri, 23 Aug 2024 15:54:59 +0200
From: Christoph Hellwig <hch@....de>
To: Segher Boessenkool <segher@...nel.crashing.org>
Cc: LEROY Christophe <christophe.leroy2@...soprasteria.com>,
Christoph Hellwig <hch@....de>,
Christian Lamparter <christian.lamparter@....uni-stuttgart.de>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>,
Stan Johnson <userm57@...oo.com>,
Finn Thain <fthain@...ux-m68k.org>
Subject: Re: [PATCH v2] powerpc: warn on emulation of dcbz instruction in
kernel mode
On Fri, Aug 23, 2024 at 08:06:00AM -0500, Segher Boessenkool wrote:
> What does "uncached memory" even mean here? Literally it would be
> I=1 memory (uncachEABLE memory), but more likely you want M=0 memory
> here ("non-memory memory", "not well-behaved memory", MMIO often).
Regular kernel memory vmapped with pgprot_noncached().
> If memset() is expected to be used with M=0, you cannot do any serious
> optimisations to it at all. If memset() is expected to be used with I=1
> it should use a separate code path for it, probably the caller should
> make the distinction.
DMA coherent memory which uses uncached memory for platforms that
do not provide hardware dma coherence can end up just about anywhere
in the kernel. We could use special routines for a few places in
the DMA subsystem, but there might be plenty of others.
Powered by blists - more mailing lists