From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention
Date: Fri, 17 Aug 2018 05:01:13 -0700 [thread overview]
Message-ID: <20180817120113.GA31542@infradead.org> (raw)
In-Reply-To: <74796f9d-5320-ea26-630a-207f4c537c55@arm.com>
On Fri, Aug 17, 2018 at 12:30:31PM +0100, Robin Murphy wrote:
> On 17/08/18 08:24, Christoph Hellwig wrote:
> > I plan to make the arm iommu dma ops generic and move them to
> > drivers/iommu for the 4.20 merge window.
>
> You mean 32-bit arm?
Sorry, I meant the arm64 wrappers for dma-iommu of course.
> The only place that code should move to is /dev/null ;)
> - the plan has always been to convert it to use groups and default domains
> so it can just plug iommu-dma in. The tricky bit is either weaning the users
> of the private arm_iommu_*() API onto generic IOMMU API usage, or at least
> implementing transitional wrappers in a way that doesn't break anything.
Agreed on the arm32 iommu code.
next prev parent reply other threads:[~2018-08-17 12:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 13:04 [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention Robin Murphy
2018-08-14 13:04 ` [PATCH 1/3] iommu: Add fast hook for getting DMA domains Robin Murphy
2018-08-17 9:36 ` John Garry
2018-08-17 11:11 ` Robin Murphy
2018-08-17 15:27 ` Laurentiu Tudor
2018-08-14 13:04 ` [PATCH 2/3] iommu/dma: Use fast DMA domain lookup Robin Murphy
2018-08-14 13:04 ` [PATCH 3/3] arm64/dma-mapping: Mildly optimise non-coherent IOMMU ops Robin Murphy
2018-08-20 15:41 ` Robin Murphy
2018-08-14 13:38 ` [PATCH 0/3] iommu: Avoid DMA ops domain refcount contention John Garry
2018-08-17 7:24 ` Christoph Hellwig
2018-08-17 9:03 ` Will Deacon
2018-08-17 11:30 ` Robin Murphy
2018-08-17 12:01 ` Christoph Hellwig [this message]
2018-08-17 13:03 ` John Garry
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=20180817120113.GA31542@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).