From: Catalin Marinas <catalin.marinas-5wv7dgnIgG8@public.gmane.org>
To: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
Cc: niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org,
will.deacon-5wv7dgnIgG8@public.gmane.org,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 1/2] iommu/dma: Implement dma_{map,unmap}_resource()
Date: Thu, 10 Nov 2016 18:37:28 +0000 [thread overview]
Message-ID: <20161110183728.GH15943@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1ae5dc0f-2e59-3e10-a61a-1f5452ad560f-5wv7dgnIgG8@public.gmane.org>
On Thu, Nov 10, 2016 at 02:30:04PM +0000, Robin Murphy wrote:
> On 10/11/16 12:24, Joerg Roedel wrote:
> > On Wed, Oct 26, 2016 at 06:43:56PM +0100, Robin Murphy wrote:
> >> With the new dma_{map,unmap}_resource() functions added to the DMA API
> >> for the benefit of cases like slave DMA, add suitable implementations to
> >> the arsenal of our generic layer. Since cache maintenance should not be
> >> a concern, these can both be standalone callback implementations without
> >> the need for arch code wrappers.
> >>
> >> CC: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
> >> Signed-off-by: Robin Murphy <robin.murphy-5wv7dgnIgG8@public.gmane.org>
> >> ---
> >>
> >> v2: Use iommu_dma_unmap_page for symmetry, instead of being sneaky.
> >>
> >> drivers/iommu/dma-iommu.c | 13 +++++++++++++
> >> include/linux/dma-iommu.h | 4 ++++
> >> 2 files changed, 17 insertions(+)
> >>
> >> diff --git a/drivers/iommu/dma-iommu.c b/drivers/iommu/dma-iommu.c
> >> index c5ab8667e6f2..a2fd90a6a782 100644
> >> --- a/drivers/iommu/dma-iommu.c
> >> +++ b/drivers/iommu/dma-iommu.c
> >> @@ -624,6 +624,19 @@ void iommu_dma_unmap_sg(struct device *dev, struct scatterlist *sg, int nents,
> >> __iommu_dma_unmap(iommu_get_domain_for_dev(dev), sg_dma_address(sg));
> >> }
> >>
> >> +dma_addr_t iommu_dma_map_resource(struct device *dev, phys_addr_t phys,
> >> + size_t size, enum dma_data_direction dir, unsigned long attrs)
> >> +{
> >> + return iommu_dma_map_page(dev, phys_to_page(phys), offset_in_page(phys),
> >> + size, dma_direction_to_prot(dir, false) | IOMMU_MMIO);
> >> +}
> >
> > Isn't the whole point of map_resource that we can map regions which have
> > no 'struct page' associated? The use phys_to_page() will certainly not
> > do the right thing here.
>
> Perhaps it's a bit cheeky, but the struct page pointer is never
> dereferenced - the only thing iommu_dma_map_page() does with it is
> immediately convert it back again. Is there ever a case where
> page_to_phys(phys_to_page(phys)) != phys ?
Without SPARSEMEM_VMEMMAP or FLATMEM, it wouldn't work. For example,
__page_to_pfn() in the SPARSEMEM case, used by page_to_phys(), even
accesses the page structure (through page_to_section()).
If the page struct is not relevant to the iommu code in question, you
could factor it out into an __iommu_dma_map_pfn(). Or maybe move the
whole logic to iommu_dma_map_resource() and call it from
iommu_dma_map_page() with the page_to_phys(page) argument.
--
Catalin
prev parent reply other threads:[~2016-11-10 18:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-26 17:43 [PATCH v2 1/2] iommu/dma: Implement dma_{map,unmap}_resource() Robin Murphy
[not found] ` <4e84146ae49a4edd5f1226d76617be9aa92a58ee.1477503578.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2016-10-26 17:43 ` [PATCH v2 2/2] arm64: Wire up iommu_dma_{map, unmap}_resource() Robin Murphy
2016-11-10 12:24 ` [PATCH v2 1/2] iommu/dma: Implement dma_{map,unmap}_resource() Joerg Roedel
[not found] ` <20161110122420.GH9996-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2016-11-10 14:30 ` Robin Murphy
[not found] ` <1ae5dc0f-2e59-3e10-a61a-1f5452ad560f-5wv7dgnIgG8@public.gmane.org>
2016-11-10 18:37 ` Catalin Marinas [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=20161110183728.GH15943@e104818-lin.cambridge.arm.com \
--to=catalin.marinas-5wv7dgnigg8@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=niklas.soderlund+renesas-1zkq55x86MTxsAP9Fp7wbw@public.gmane.org \
--cc=robin.murphy-5wv7dgnIgG8@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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).