lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Oct 2023 07:52:13 +0200
From: Christoph Hellwig <>
To: Greg Ungerer <>
Cc: Robin Murphy <>, Christoph Hellwig <>,, Marek Szyprowski <>,
	Geert Uytterhoeven <>,
	Wei Fang <>, Shenwei Wang <>,
	Clark Wang <>,
	NXP Linux Team <>,,, Jim Quinlan <>
Subject: Re: [PATCH 5/6] net: fec: use dma_alloc_noncoherent for m532x

On Wed, Oct 11, 2023 at 12:20:57AM +1000, Greg Ungerer wrote:
> That should be M532x.
> I am pretty sure the code as-is today is broken for the case of using
> the split cache arrangement (so both instruction and data cache) for any
> of the version 2 cores too (denoted by the HAVE_CACHE_SPLIT option).
> But that has probably not been picked up because the default on those
> has always been instruction cache only.
> The reason for the special case for the M532x series is that it is a version 3
> core and they have a unified instruction and data cache. The 523x series is the
> only version 3 core that Linux supports that has the FEC hardware module.

So what config option should we check for supporting coherent allocations
and which not having the hack in fec?

Here is my guesses based on the above:

in m68k support coherent allocations with no work if

is set.

in the fec driver do the alloc_noncoherent and global cache flush
hack if:



Powered by blists - more mailing lists