From: Samiullah Khawaja <skhawaja@google.com>
To: Marek Szyprowski <m.szyprowski@samsung.com>,
Will Deacon <will@kernel.org>, Jason Gunthorpe <jgg@ziepe.ca>
Cc: Samiullah Khawaja <skhawaja@google.com>,
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>,
Pranjal Shrivastava <praan@google.com>,
Vipin Sharma <vipinsh@google.com>
Subject: [RFC PATCH 0/4] dma-mapping: Add preservation of direct allocations
Date: Tue, 5 May 2026 00:23:16 +0000 [thread overview]
Message-ID: <20260505002320.2210067-1-skhawaja@google.com> (raw)
This is an RFC to discuss the preservation of DMA allocations for
devices that are using direct allocation mode. Note preservation here
means preservation of physical memory only using KHO. IOVAs and IOMMU
mappings are out of scope.
The complexity and need of this was discussed in the thread mentioned
below. It was proposed to allow preservation of only a subset of
allocations with minimum support.
https://lore.kernel.org/all/aepfYzkI7NsVGCF0@google.com/
https://lore.kernel.org/all/aepRy7Gp7Ng85Zr7@willie-the-truck/
Note DMA allocation allows allocation from various allocators in various
configurations. This RFC supports preservation with,
- Direct Allocation Only.
- Pages allocated through alloc_page (Buddy allocator).
- No CMA support.
- No DMA allocators.
The changes are also pushed here:
https://github.com/samikhawaja/linux/tree/dma-alloc-preserve-direct
Looking forward to your feedback on this.
Thanks
Samiullah Khawaja (4):
dma: Add DMA allocation preservation KHO ABI
dma/pool: Add an API to check if DMA allocation is from pool
dma-direct: Add API to preserve/restore allocations
dma-mapping: Add API to preserve/restore DMA allocation
include/linux/dma-direct.h | 29 ++++++
include/linux/dma-map-ops.h | 1 +
include/linux/dma-mapping.h | 50 +++++++++
include/linux/kho/abi/dma_alloc.h | 30 ++++++
kernel/dma/Kconfig | 3 +
kernel/dma/direct.c | 163 ++++++++++++++++++++++++++++++
kernel/dma/mapping.c | 52 ++++++++++
kernel/dma/pool.c | 13 +++
8 files changed, 341 insertions(+)
create mode 100644 include/linux/kho/abi/dma_alloc.h
base-commit: 9974969c14031a097d6b45bcb7a06bb4aa525c40
prerequisite-patch-id: 41f13f37cb3b439f17dfa4e3f2d5c767aaef0346
--
2.54.0.545.g6539524ca2-goog
next reply other threads:[~2026-05-05 0:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 0:23 Samiullah Khawaja [this message]
2026-05-05 0:29 ` [RFC PATCH 0/4] dma-mapping: Add preservation of direct allocations Samiullah Khawaja
-- strict thread matches above, loose matches on Subject: below --
2026-05-05 0:27 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=20260505002320.2210067-1-skhawaja@google.com \
--to=skhawaja@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=praan@google.com \
--cc=pratyush@kernel.org \
--cc=robin.murphy@arm.com \
--cc=rppt@kernel.org \
--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