[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aDhCPZwmH515TJav@Red>
Date: Thu, 29 May 2025 13:17:17 +0200
From: Corentin Labbe <clabbe.montjoie@...il.com>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Klaus Kudielka <klaus.kudielka@...il.com>,
Eric Biggers <ebiggers@...nel.org>, regressions@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Linux Crypto Mailing List <linux-crypto@...r.kernel.org>,
Boris Brezillon <bbrezillon@...nel.org>,
EBALARD Arnaud <Arnaud.Ebalard@....gouv.fr>,
Romain Perier <romain.perier@...il.com>,
Arnd Bergmann <arnd@...db.de>, Andrew Lunn <andrew@...n.ch>,
Sebastian Hesselbarth <sebastian.hesselbarth@...il.com>,
Gregory Clement <gregory.clement@...tlin.com>,
Christoph Hellwig <hch@...radead.org>,
Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>
Subject: Re: crypto: marvell/cesa - dma_alloc_coherent broken but kmalloc +
dma_map_single works
Le Wed, May 28, 2025 at 05:58:13PM +0800, Herbert Xu a écrit :
> On Thu, May 22, 2025 at 10:07:54PM +0200, Corentin Labbe wrote:
> >
> > Here is the result:
> > http://kernel.montjoie.ovh/479404.log
> >
> > I have built by adding also your "crypto: marvell/cesa - Fix engine load inaccuracy"
>
> Please try this patch on top of the current mainline tree.
>
> I've force-enabled the software finalisation code and switched it
> over to kmalloc + dma_map_single.
>
> Thanks,
> --
Hello
I have tried on top of torvalds/master 90b83efa6701656e02c86e7df2cb1765ea602d07
https://kernel.montjoie.ovh/479785.log
Regards
Powered by blists - more mailing lists