From: Mostafa Saleh <smostafa@google.com>
To: "Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>
Cc: iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, m.szyprowski@samsung.com, will@kernel.org,
maz@kernel.org, suzuki.poulose@arm.com, catalin.marinas@arm.com,
jiri@resnulli.us, jgg@ziepe.ca
Subject: Re: [PATCH v2 0/8] dma-mapping: Use DMA_ATTR_CC_SHARED through direct, pool and swiotlb paths
Date: Tue, 2 Jun 2026 14:25:12 +0000 [thread overview]
Message-ID: <ah7nyK0-XVUM74rO@google.com> (raw)
In-Reply-To: <20260420061415.3650870-1-aneesh.kumar@kernel.org>
On Mon, Apr 20, 2026 at 11:44:07AM +0530, Aneesh Kumar K.V (Arm) wrote:
> This series propagates DMA_ATTR_CC_SHARED through the dma-direct,
> dma-pool, and swiotlb paths so that encrypted and decrypted DMA buffers
> are handled consistently.
>
> Today, the direct DMA path mostly relies on force_dma_unencrypted() for
> shared/decrypted buffer handling. This series consolidates the
> force_dma_unencrypted() checks in the top-level functions and ensures
> that the remaining DMA interfaces use DMA attributes to make the correct
> decisions.
I tested this series on protected KVM and did not see regressions.
Tested-by: Mostafa Saleh <smostafa@google.com>
Next, I will:
- Send the pKVM CC patch separately.
- Review this series.
Thanks,
Mostafa
>
> The series:
> - moves swiotlb-backed allocations out of __dma_direct_alloc_pages(),
> - propagates DMA_ATTR_CC_SHARED through the dma-direct alloc/free
> paths,
> - teaches the atomic DMA pools to track encrypted versus decrypted
> state,
> - tracks swiotlb pool encryption state and enforces strict pool
> selection,
> - centralizes encrypted/decrypted pgprot handling in dma_pgprot() using
> DMA attributes,
> - makes dma_direct_map_phys() choose the DMA address encoding from
> attrs, and
> - uses the selected swiotlb pool state to derive the returned DMA
> address.
>
> Changes from v1:
> * rebased to latest kernel (change from DMA_ATTR_CC_DECRYPTED -> DMA_ATTR_CC_SHARED)
> * Update alloc path such that DMA_ATTR_CC_SHARED s not a caller-visible attribute.
>
> Aneesh Kumar K.V (Arm) (8):
> dma-direct: swiotlb: handle swiotlb alloc/free outside
> __dma_direct_alloc_pages
> dma-direct: use DMA_ATTR_CC_SHARED in alloc/free paths
> dma-pool: track decrypted atomic pools and select them via attrs
> dma: swiotlb: track pool encryption state and honor DMA_ATTR_CC_SHARED
> dma-mapping: make dma_pgprot() honor DMA_ATTR_CC_SHARED
> dma-direct: make dma_direct_map_phys() honor DMA_ATTR_CC_SHARED
> dma-direct: set decrypted flag for remapped DMA allocations
> dma-direct: select DMA address encoding from DMA_ATTR_CC_SHARED
>
> drivers/iommu/dma-iommu.c | 2 +-
> include/linux/dma-direct.h | 10 ++
> include/linux/dma-map-ops.h | 2 +-
> include/linux/swiotlb.h | 7 +-
> kernel/dma/direct.c | 185 ++++++++++++++++++++++++++++--------
> kernel/dma/direct.h | 25 ++---
> kernel/dma/mapping.c | 16 +++-
> kernel/dma/pool.c | 154 +++++++++++++++++++-----------
> kernel/dma/swiotlb.c | 89 +++++++++++++----
> 9 files changed, 355 insertions(+), 135 deletions(-)
>
>
> base-commit: c1f49dea2b8f335813d3b348fd39117fb8efb428
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-06-02 14:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 6:14 [PATCH v2 0/8] dma-mapping: Use DMA_ATTR_CC_SHARED through direct, pool and swiotlb paths Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 1/8] dma-direct: swiotlb: handle swiotlb alloc/free outside __dma_direct_alloc_pages Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 2/8] dma-direct: use DMA_ATTR_CC_SHARED in alloc/free paths Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 3/8] dma-pool: track decrypted atomic pools and select them via attrs Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 4/8] dma: swiotlb: track pool encryption state and honor DMA_ATTR_CC_SHARED Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 5/8] dma-mapping: make dma_pgprot() " Aneesh Kumar K.V (Arm)
2026-04-20 6:14 ` [PATCH v2 6/8] dma-direct: make dma_direct_map_phys() " Aneesh Kumar K.V (Arm)
2026-04-21 12:29 ` Jason Gunthorpe
2026-04-22 5:50 ` Aneesh Kumar K.V
2026-04-22 6:16 ` Aneesh Kumar K.V
2026-04-24 22:45 ` Jason Gunthorpe
2026-04-24 22:41 ` Jason Gunthorpe
2026-04-20 6:14 ` [PATCH v2 7/8] dma-direct: set decrypted flag for remapped DMA allocations Aneesh Kumar K.V (Arm)
2026-04-21 12:34 ` Jason Gunthorpe
2026-04-21 12:54 ` Suzuki K Poulose
2026-04-21 13:53 ` Jason Gunthorpe
2026-04-22 5:24 ` Aneesh Kumar K.V
2026-04-20 6:14 ` [PATCH v2 8/8] dma-direct: select DMA address encoding from DMA_ATTR_CC_SHARED Aneesh Kumar K.V (Arm)
2026-04-21 12:40 ` [PATCH v2 0/8] dma-mapping: Use DMA_ATTR_CC_SHARED through direct, pool and swiotlb paths Jason Gunthorpe
2026-06-02 14:25 ` Mostafa Saleh [this message]
2026-06-02 14:29 ` Mostafa Saleh
2026-06-03 4:57 ` Aneesh Kumar K.V
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=ah7nyK0-XVUM74rO@google.com \
--to=smostafa@google.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maz@kernel.org \
--cc=robin.murphy@arm.com \
--cc=suzuki.poulose@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