From: Robin Murphy <robin.murphy@arm.com>
To: Christoph Hellwig <hch@lst.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Tomasz Figa <tfiga@chromium.org>,
Ricardo Ribalda <ribalda@chromium.org>,
Sergey Senozhatsky <senozhatsky@google.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
iommu@lists.linux-foundation.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 3/6] dma-mapping: add a dma_alloc_noncontiguous API
Date: Thu, 29 Jun 2023 18:20:58 +0100 [thread overview]
Message-ID: <94d4b082-7b08-82e0-bb42-6ac36821ea61@arm.com> (raw)
In-Reply-To: <20210301085236.947011-4-hch@lst.de>
[Archaeology ensues...]
On 2021-03-01 08:52, Christoph Hellwig wrote:
[...]
> +static struct sg_table *alloc_single_sgt(struct device *dev, size_t size,
> + enum dma_data_direction dir, gfp_t gfp)
> +{
> + struct sg_table *sgt;
> + struct page *page;
> +
> + sgt = kmalloc(sizeof(*sgt), gfp);
> + if (!sgt)
> + return NULL;
> + if (sg_alloc_table(sgt, 1, gfp))
> + goto out_free_sgt;
> + page = __dma_alloc_pages(dev, size, &sgt->sgl->dma_address, dir, gfp);
> + if (!page)
> + goto out_free_table;
> + sg_set_page(sgt->sgl, page, PAGE_ALIGN(size), 0);
> + sg_dma_len(sgt->sgl) = sgt->sgl->length;
> + return sgt;
> +out_free_table:
> + sg_free_table(sgt);
> +out_free_sgt:
> + kfree(sgt);
> + return NULL;
> +}
> +
> +struct sg_table *dma_alloc_noncontiguous(struct device *dev, size_t size,
> + enum dma_data_direction dir, gfp_t gfp, unsigned long attrs)
> +{
> + const struct dma_map_ops *ops = get_dma_ops(dev);
> + struct sg_table *sgt;
> +
> + if (WARN_ON_ONCE(attrs & ~DMA_ATTR_ALLOC_SINGLE_PAGES))
> + return NULL;
> +
> + if (ops && ops->alloc_noncontiguous)
> + sgt = ops->alloc_noncontiguous(dev, size, dir, gfp, attrs);
> + else
> + sgt = alloc_single_sgt(dev, size, dir, gfp);
> +
> + if (sgt) {
> + sgt->nents = 1;
> + debug_dma_map_sg(dev, sgt->sgl, sgt->orig_nents, 1, dir);
It turns out this is liable to trip up DMA_API_DEBUG_SG (potentially
even in the alloc_single_sgt() case), since we've filled in sgt without
paying attention to the device's segment boundary/size parameters.
Now, it would be entirely possible to make the allocators "properly"
partition the pages into multiple segments per those constraints, but
given that there's no actual dma_map_sg() operation involved, and AFAIR
the intent here is really only to describe a single DMA-contiguous
buffer as pages, rather than represent a true scatter-gather operation,
I'm now wondering whether it makes more sense to just make dma-debug a
bit cleverer instead. Any other opinions?
Thanks,
Robin.
> + }
> + return sgt;
> +}
next prev parent reply other threads:[~2023-06-29 17:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 8:52 add a new dma_alloc_noncontiguous API v3 Christoph Hellwig
2021-03-01 8:52 ` [PATCH 1/6] dma-mapping: add a dma_mmap_pages helper Christoph Hellwig
2021-03-01 8:52 ` [PATCH 2/6] dma-mapping: refactor dma_{alloc,free}_pages Christoph Hellwig
2021-03-01 8:52 ` [PATCH 3/6] dma-mapping: add a dma_alloc_noncontiguous API Christoph Hellwig
2023-06-29 17:20 ` Robin Murphy [this message]
2023-07-05 11:16 ` Tomasz Figa
2021-03-01 8:52 ` [PATCH 4/6] dma-iommu: refactor iommu_dma_alloc_remap Christoph Hellwig
2021-03-01 8:52 ` [PATCH 5/6] dma-iommu: implement ->alloc_noncontiguous Christoph Hellwig
2021-03-01 8:52 ` [PATCH 6/6] media: uvcvideo: Use dma_alloc_noncontiguos API Christoph Hellwig
2021-03-12 1:42 ` Laurent Pinchart
2021-03-12 1:43 ` Laurent Pinchart
2021-03-11 16:52 ` add a new dma_alloc_noncontiguous API v3 Christoph Hellwig
2021-03-11 16:57 ` Ricardo Ribalda
-- strict thread matches above, loose matches on Subject: below --
2021-01-28 14:58 add a new dma_alloc_noncontiguous API Christoph Hellwig
2021-01-28 14:58 ` [PATCH 3/6] dma-mapping: add a " 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=94d4b082-7b08-82e0-bb42-6ac36821ea61@arm.com \
--to=robin.murphy@arm.com \
--cc=hch@lst.de \
--cc=iommu@lists.linux-foundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mchehab@kernel.org \
--cc=ribalda@chromium.org \
--cc=senozhatsky@google.com \
--cc=tfiga@chromium.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
all inboxes | Powered by JetHome®