All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: linux-kernel@vger.kernel.org, jeremy.linton@arm.com,
	iommu@lists.linux-foundation.org,
	linux-rpi-kernel@lists.infradead.org,
	David Rientjes <rientjes@google.com>,
	Robin Murphy <robin.murphy@arm.com>,
	hch@lst.de
Subject: Re: [PATCH v2 0/4] dma-pool: Fix atomic pool selection
Date: Wed, 15 Jul 2020 09:12:56 +0200	[thread overview]
Message-ID: <20200715071256.GA22500@lst.de> (raw)
In-Reply-To: <20200714123928.8581-1-nsaenzjulienne@suse.de>

On Tue, Jul 14, 2020 at 02:39:24PM +0200, 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.

I've applied the series as well as that patch to the dma-mapping tree,
thanks.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: hch@lst.de, linux-kernel@vger.kernel.org,
	linux-rpi-kernel@lists.infradead.org, jeremy.linton@arm.com,
	Robin Murphy <robin.murphy@arm.com>,
	David Rientjes <rientjes@google.com>,
	iommu@lists.linux-foundation.org
Subject: Re: [PATCH v2 0/4] dma-pool: Fix atomic pool selection
Date: Wed, 15 Jul 2020 09:12:56 +0200	[thread overview]
Message-ID: <20200715071256.GA22500@lst.de> (raw)
In-Reply-To: <20200714123928.8581-1-nsaenzjulienne@suse.de>

On Tue, Jul 14, 2020 at 02:39:24PM +0200, 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.

I've applied the series as well as that patch to the dma-mapping tree,
thanks.

  parent reply	other threads:[~2020-07-15  7:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-14 12:39 [PATCH v2 0/4] dma-pool: Fix atomic pool selection Nicolas Saenz Julienne
2020-07-14 12:39 ` Nicolas Saenz Julienne
2020-07-14 12:39 ` [PATCH v2 1/4] dma-direct: Provide function to check physical memory area validity Nicolas Saenz Julienne
2020-07-14 12:39   ` Nicolas Saenz Julienne
2020-07-14 12:39 ` [PATCH v2 2/4] dma-pool: Get rid of dma_in_atomic_pool() Nicolas Saenz Julienne
2020-07-14 12:39   ` Nicolas Saenz Julienne
2020-07-14 12:39 ` [PATCH v2 3/4] dma-pool: Introduce dma_guess_pool() Nicolas Saenz Julienne
2020-07-14 12:39   ` Nicolas Saenz Julienne
2020-07-14 12:39 ` [PATCH v2 4/4] dma-pool: Make sure atomic pool suits device Nicolas Saenz Julienne
2020-07-14 12:39   ` Nicolas Saenz Julienne
2020-07-15  7:12 ` Christoph Hellwig [this message]
2020-07-15  7:12   ` [PATCH v2 0/4] dma-pool: Fix atomic pool selection Christoph Hellwig

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=20200715071256.GA22500@lst.de \
    --to=hch@lst.de \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jeremy.linton@arm.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.