From: Pranjal Shrivastava <praan@google.com>
To: Samiullah Khawaja <skhawaja@google.com>
Cc: Marek Szyprowski <m.szyprowski@samsung.com>,
Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Mike Rapoport <rppt@kernel.org>,
Pratyush Yadav <pratyush@kernel.org>,
Alexander Graf <graf@amazon.com>,
Robin Murphy <robin.murphy@arm.com>,
Kevin Tian <kevin.tian@intel.com>,
iommu@lists.linux.dev, kexec@lists.infradead.org,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
David Matlack <dmatlack@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vipin Sharma <vipinsh@google.com>
Subject: Re: [RFC PATCH 2/4] dma/pool: Add an API to check if DMA allocation is from pool
Date: Mon, 8 Jun 2026 18:10:02 +0000 [thread overview]
Message-ID: <aicFes0uxUFQAduC@google.com> (raw)
In-Reply-To: <20260505002737.2213734-3-skhawaja@google.com>
On Tue, May 05, 2026 at 12:27:35AM +0000, Samiullah Khawaja wrote:
> DMA allocations can be done through DMA pools, add an API that can be
> used to check if an allocation is done from a pool. This will be used in
> the later commit during preservation of DMA allocation.
>
> Signed-off-by: Samiullah Khawaja <skhawaja@google.com>
> ---
> include/linux/dma-map-ops.h | 1 +
> kernel/dma/pool.c | 13 +++++++++++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/include/linux/dma-map-ops.h b/include/linux/dma-map-ops.h
> index 6a1832a73cad..6a0bc4ea2467 100644
> --- a/include/linux/dma-map-ops.h
> +++ b/include/linux/dma-map-ops.h
> @@ -216,6 +216,7 @@ struct page *dma_alloc_from_pool(struct device *dev, size_t size,
> bool (*phys_addr_ok)(struct device *, phys_addr_t, size_t));
> bool dma_free_from_pool(struct device *dev, void *start, size_t size);
>
> +bool dma_is_from_pool(struct device *dev, void *start, size_t size);
> int dma_direct_set_offset(struct device *dev, phys_addr_t cpu_start,
> dma_addr_t dma_start, u64 size);
>
> diff --git a/kernel/dma/pool.c b/kernel/dma/pool.c
> index 2b2fbb709242..32ce4d6d7683 100644
> --- a/kernel/dma/pool.c
> +++ b/kernel/dma/pool.c
> @@ -307,3 +307,16 @@ bool dma_free_from_pool(struct device *dev, void *start, size_t size)
>
> return false;
> }
> +
> +bool dma_is_from_pool(struct device *dev, void *start, size_t size)
Do we need struct device here? It seems unused?
Nit: we only ever pass 0 gfp_flags to dma_guess_pool, should we instead
name it: dma_is_from_atomic_pool() to be more accurate?
> +{
> + struct gen_pool *pool = NULL;
> +
> + while ((pool = dma_guess_pool(pool, 0))) {
> + if (!gen_pool_has_addr(pool, (unsigned long)start, size))
> + continue;
> + return true;
> + }
Nit: The loop looks slightly ugly, can we have:
struct gen_pool *pool;
for (pool = dma_guess_pool(NULL, 0); pool != NULL; pool = dma_guess_pool(pool, 0)) {
if (gen_pool_has_addr(pool, (unsigned long)start, size))
return true;
}
> +
> + return false;
> +}
> --
> 2.54.0.545.g6539524ca2-goog
>
Thanks,
Praan
next prev parent reply other threads:[~2026-06-08 18:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 0:27 [RFC PATCH 0/4] dma-mapping: Add preservation of direct allocations Samiullah Khawaja
2026-05-05 0:27 ` [RFC PATCH 1/4] dma: Add DMA allocation preservation KHO ABI Samiullah Khawaja
2026-06-08 17:53 ` Pranjal Shrivastava
2026-05-05 0:27 ` [RFC PATCH 2/4] dma/pool: Add an API to check if DMA allocation is from pool Samiullah Khawaja
2026-06-08 18:10 ` Pranjal Shrivastava [this message]
2026-05-05 0:27 ` [RFC PATCH 3/4] dma-direct: Add API to preserve/restore allocations Samiullah Khawaja
2026-06-01 12:35 ` Will Deacon
2026-06-02 20:14 ` Samiullah Khawaja
2026-06-08 19:55 ` Pranjal Shrivastava
2026-05-05 0:27 ` [RFC PATCH 4/4] dma-mapping: Add API to preserve/restore DMA allocation Samiullah Khawaja
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=aicFes0uxUFQAduC@google.com \
--to=praan@google.com \
--cc=akpm@linux-foundation.org \
--cc=dmatlack@google.com \
--cc=graf@amazon.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=kevin.tian@intel.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=pasha.tatashin@soleen.com \
--cc=pratyush@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--cc=skhawaja@google.com \
--cc=vipinsh@google.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