From: Jason Gunthorpe <jgg@ziepe.ca>
To: Mostafa Saleh <smostafa@google.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
"Aneesh Kumar K.V (Arm)" <aneesh.kumar@kernel.org>,
iommu@lists.linux.dev, linux-kernel@vger.kernel.org,
Robin Murphy <robin.murphy@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Will Deacon <will@kernel.org>, Marc Zyngier <maz@kernel.org>,
Steven Price <steven.price@arm.com>,
Suzuki K Poulose <Suzuki.Poulose@arm.com>,
Jiri Pirko <jiri@resnulli.us>, Petr Tesarik <ptesarik@suse.com>,
Alexey Kardashevskiy <aik@amd.com>,
Dan Williams <dan.j.williams@intel.com>,
Xu Yilun <yilun.xu@linux.intel.com>
Subject: Re: [PATCH v3 0/9] dma-mapping: Use DMA_ATTR_CC_SHARED through direct, pool and swiotlb paths
Date: Tue, 12 May 2026 09:42:06 -0300 [thread overview]
Message-ID: <20260512124206.GV9285@ziepe.ca> (raw)
In-Reply-To: <agG557zSEmAqp1mn@google.com>
On Mon, May 11, 2026 at 11:13:43AM +0000, Mostafa Saleh wrote:
> On Fri, May 08, 2026 at 06:28:11PM +0100, Catalin Marinas wrote:
> > On Mon, Apr 27, 2026 at 11:25:00AM +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.
> >
> > I think this series makes sense, using DMA_ATTR_CC_SHARED throughout the
> > DMA API, either for alloc or for streaming to decide/check what bouncing
> > does. Sashiko has a few interesting reports, it probably breaks s390 as
> > well (it might be similar to the pKVM case).
>
> I have this series on my review list, I believe there is an overlap with
> my series, I can rebase mine on top of this if that makes sense, I will
> probably wait for a new version to address the current comments and
> Sashiko notes.
I've been wondering about the two series as well.. I think this is a
big help to your project, but it would be nice to know??
Jason
next prev parent reply other threads:[~2026-05-12 12:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260427055509.898190-1-aneesh.kumar@kernel.org>
[not found] ` <20260427055509.898190-3-aneesh.kumar@kernel.org>
2026-05-08 9:26 ` [PATCH v3 2/9] dma-direct: use DMA_ATTR_CC_SHARED in alloc/free paths Catalin Marinas
2026-05-11 5:38 ` Aneesh Kumar K.V
[not found] ` <20260427055509.898190-5-aneesh.kumar@kernel.org>
2026-05-08 16:49 ` [PATCH v3 4/9] dma: swiotlb: track pool encryption state and honor DMA_ATTR_CC_SHARED Catalin Marinas
2026-05-11 5:14 ` Aneesh Kumar K.V
2026-05-08 17:28 ` [PATCH v3 0/9] dma-mapping: Use DMA_ATTR_CC_SHARED through direct, pool and swiotlb paths Catalin Marinas
2026-05-10 0:36 ` Jason Gunthorpe
2026-05-11 11:13 ` Mostafa Saleh
2026-05-12 12:42 ` Jason Gunthorpe [this message]
2026-05-11 11:18 ` 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=20260512124206.GV9285@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Suzuki.Poulose@arm.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dan.j.williams@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=maz@kernel.org \
--cc=ptesarik@suse.com \
--cc=robin.murphy@arm.com \
--cc=smostafa@google.com \
--cc=steven.price@arm.com \
--cc=will@kernel.org \
--cc=yilun.xu@linux.intel.com \
/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