From: Leon Romanovsky <leon@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Christoph Hellwig <hch@lst.de>, Joerg Roedel <joro@8bytes.org>,
Will Deacon <will@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev,
Jason Gunthorpe <jgg@nvidia.com>
Subject: Re: [PATCH 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks
Date: Fri, 12 Jul 2024 08:47:25 +0300 [thread overview]
Message-ID: <20240712054725.GD1815706@unreal> (raw)
In-Reply-To: <7ef6cd1e-3dc6-452e-ac1c-128ee98acdb0@arm.com>
On Thu, Jul 11, 2024 at 07:02:39PM +0100, Robin Murphy wrote:
> On 11/07/2024 11:38 am, Leon Romanovsky wrote:
> > From: Leon Romanovsky <leonro@nvidia.com>
> >
> > Almost all users of ->map_page()/map_sg() callbacks implement
> > ->unmap_page()/unmap_sg() callbacks too. One user which doesn't do it,
> > is dummy DMA ops interface, and the use of this interface is to fail
> > the operation and in such case, there won't be any call to
> > ->unmap_page()/unmap_sg().
> >
> > This patch removes the existence checks of ->unmap_page()/unmap_sg()
> > and calls to it directly to create symmetrical interface to
> > ->map_page()/map_sg().
>
> Now that all the common cases have been mopped up by dma-direct, I'm
> inclined to agree that this seems reasonable. For sure there is code out
> there still abusing random DMA API calls as a cache maintenance interface
> because it thinks it knows better, but even that's going to be running on
> platforms where it expects unmap to have the desired effect anyway, so the
> chance of somehow ending up with the dummy ops and crashing seems
> sufficiently unlikely.
>
> However, I'm a little wary of the static checker brigade noticing that and
> trying to "fix" it by reinstating these tests, so perhaps it's worth just
> adding unmaps to the dummy ops (with a WARN() in them) as well for the sake
> of cleanliness and avoidance of any doubt.
I'll add, however the plan is to get rid of dummy ops in the near future.
Thanks
>
> Thanks,
> Robin.
>
> > Signed-off-by: Leon Romanovsky <leonro@nvidia.com>
> > ---
> > kernel/dma/mapping.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/kernel/dma/mapping.c b/kernel/dma/mapping.c
> > index 81de84318ccc..6832fd6f0796 100644
> > --- a/kernel/dma/mapping.c
> > +++ b/kernel/dma/mapping.c
> > @@ -177,7 +177,7 @@ void dma_unmap_page_attrs(struct device *dev, dma_addr_t addr, size_t size,
> > if (dma_map_direct(dev, ops) ||
> > arch_dma_unmap_page_direct(dev, addr + size))
> > dma_direct_unmap_page(dev, addr, size, dir, attrs);
> > - else if (ops->unmap_page)
> > + else
> > ops->unmap_page(dev, addr, size, dir, attrs);
> > debug_dma_unmap_page(dev, addr, size, dir);
> > }
> > @@ -291,7 +291,7 @@ void dma_unmap_sg_attrs(struct device *dev, struct scatterlist *sg,
> > if (dma_map_direct(dev, ops) ||
> > arch_dma_unmap_sg_direct(dev, sg, nents))
> > dma_direct_unmap_sg(dev, sg, nents, dir, attrs);
> > - else if (ops->unmap_sg)
> > + else
> > ops->unmap_sg(dev, sg, nents, dir, attrs);
> > }
> > EXPORT_SYMBOL(dma_unmap_sg_attrs);
prev parent reply other threads:[~2024-07-12 5:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-11 10:38 [PATCH 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks Leon Romanovsky
2024-07-11 10:38 ` [PATCH 2/2] dma: Add IOMMU static calls with clear default ops Leon Romanovsky
2024-07-11 17:27 ` Leon Romanovsky
2024-07-11 18:17 ` Easwar Hariharan
2024-07-11 18:45 ` Leon Romanovsky
2024-07-11 18:23 ` Robin Murphy
2024-07-11 18:57 ` Leon Romanovsky
2024-07-11 20:08 ` Robin Murphy
2024-07-12 5:50 ` Leon Romanovsky
2024-07-12 14:21 ` Robin Murphy
2024-07-13 5:18 ` Christoph Hellwig
2024-07-13 9:32 ` Leon Romanovsky
2024-07-12 4:49 ` Christoph Hellwig
2024-07-12 6:02 ` Leon Romanovsky
2024-07-12 20:51 ` Easwar Hariharan
2024-07-13 9:30 ` Leon Romanovsky
2024-07-11 18:02 ` [PATCH 1/2] dma: call unconditionally to unmap_page and unmap_sg callbacks Robin Murphy
2024-07-12 5:47 ` Leon Romanovsky [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=20240712054725.GD1815706@unreal \
--to=leon@kernel.org \
--cc=hch@lst.de \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=robin.murphy@arm.com \
--cc=will@kernel.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