From: Jeremy Linton <jeremy.linton@arm.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
hch@lst.de, Robin Murphy <robin.murphy@arm.com>,
David Rientjes <rientjes@google.com>,
iommu@lists.linux-foundation.org
Cc: linux-rpi-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] dma-pool: Fix atomic pool selection
Date: Fri, 10 Jul 2020 13:52:59 -0500 [thread overview]
Message-ID: <c28da389-dae5-9bc8-61f1-d40da086c5c4@arm.com> (raw)
In-Reply-To: <20200709161903.26229-1-nsaenzjulienne@suse.de>
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@arm.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(-)
>
prev parent reply other threads:[~2020-07-10 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 16:19 Nicolas Saenz Julienne
2020-07-09 16:19 ` [PATCH 1/4] dma-direct: Provide function to check physical memory area validity Nicolas Saenz Julienne
2020-07-09 16:19 ` [PATCH 2/4] dma-pool: Get rid of dma_in_atomic_pool() Nicolas Saenz Julienne
2020-07-09 21:51 ` David Rientjes
2020-07-10 6:50 ` Christoph Hellwig
2020-07-09 16:19 ` [PATCH 3/4] dma-pool: Introduce dma_guess_pool() Nicolas Saenz Julienne
2020-07-14 11:22 ` Christoph Hellwig
2020-07-14 11:40 ` Nicolas Saenz Julienne
2020-07-09 16:19 ` [PATCH 4/4] dma-pool: Make sure atomic pool suits device Nicolas Saenz Julienne
2020-07-10 18:52 ` Jeremy Linton [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c28da389-dae5-9bc8-61f1-d40da086c5c4@arm.com \
--to=jeremy.linton@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=nsaenzjulienne@suse.de \
--cc=rientjes@google.com \
--cc=robin.murphy@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®