[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c28da389-dae5-9bc8-61f1-d40da086c5c4@arm.com>
Date: Fri, 10 Jul 2020 13:52:59 -0500
From: Jeremy Linton <jeremy.linton@....com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>, hch@....de,
Robin Murphy <robin.murphy@....com>,
David Rientjes <rientjes@...gle.com>,
iommu@...ts.linux-foundation.org
Cc: linux-rpi-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/4] dma-pool: Fix atomic pool selection
Hi,
I have merged this to a 5.8 tree along with "dma-pool: Only allocate
from CMA when in the same memory zone" and tested it in various ACPI/DT
combinations, particularly on the RPI4. It seems to be working fine.
So thanks for your time and effort clearing this up!
Tested-by: Jeremy Linton <jeremy.linton@....com>
On 7/9/20 11:19 AM, Nicolas Saenz Julienne wrote:
> This is my attempt at fixing one of the regressions we've seen[1] after
> the introduction of per-zone atomic pools.
>
> This combined with "dma-pool: Do not allocate pool memory from CMA"[2]
> should fix the boot issues on Jeremy's RPi4 setup.
>
> [1] https://lkml.org/lkml/2020/7/2/974
> [2] https://lkml.org/lkml/2020/7/8/1108
>
> ---
>
> Nicolas Saenz Julienne (4):
> dma-direct: Provide function to check physical memory area validity
> dma-pool: Get rid of dma_in_atomic_pool()
> dma-pool: Introduce dma_guess_pool()
> dma-pool: Make sure atomic pool suits device
>
> include/linux/dma-direct.h | 1 +
> kernel/dma/direct.c | 2 +-
> kernel/dma/pool.c | 76 +++++++++++++++++++++++++++-----------
> 3 files changed, 56 insertions(+), 23 deletions(-)
>
Powered by blists - more mailing lists