From: Jason Gunthorpe <jgg@ziepe.ca>
To: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>
Cc: Jiri Pirko <jiri@resnulli.us>,
dri-devel@lists.freedesktop.org, linaro-mm-sig@lists.linaro.org,
iommu@lists.linux.dev, linux-media@vger.kernel.org,
sumit.semwal@linaro.org, benjamin.gaignard@collabora.com,
Brian.Starkey@arm.com, jstultz@google.com, tjmercier@google.com,
christian.koenig@amd.com, m.szyprowski@samsung.com,
robin.murphy@arm.com, leon@kernel.org, sean.anderson@linux.dev,
ptesarik@suse.com, catalin.marinas@arm.com,
suzuki.poulose@arm.com, steven.price@arm.com,
thomas.lendacky@amd.com, john.allen@amd.com,
ashish.kalra@amd.com, suravee.suthikulpanit@amd.com,
linux-coco@lists.linux.dev
Subject: Re: [PATCH v5 1/2] dma-mapping: introduce DMA_ATTR_CC_SHARED for shared memory
Date: Fri, 22 May 2026 10:22:40 -0300 [thread overview]
Message-ID: <20260522132240.GD7702@ziepe.ca> (raw)
In-Reply-To: <yq5aqzn45a81.fsf@kernel.org>
On Fri, May 22, 2026 at 10:09:26AM +0530, Aneesh Kumar K.V wrote:
> Can I convert this as an independent patch with your SOB?
Sure,
Maybe you can ignore it for your series, the intersection of CC and
P2P is non-existant right now. HW doesn't support it. Make the DMA API
follow the design assuming this patch is applied.
Jason
next prev parent reply other threads:[~2026-05-22 13:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260325192400eucas1p2ae38ff4c2b3ab35a7047cfd680d9fda3@eucas1p2.samsung.com>
2026-03-25 19:23 ` [PATCH v5 0/2] dma-buf: heaps: system: add an option to allocate explicitly shared/decrypted memory Jiri Pirko
2026-03-25 19:23 ` [PATCH v5 1/2] dma-mapping: introduce DMA_ATTR_CC_SHARED for shared memory Jiri Pirko
2026-03-31 15:08 ` Jason Gunthorpe
2026-04-20 6:34 ` Aneesh Kumar K.V
2026-04-20 9:29 ` Jiri Pirko
2026-04-21 9:42 ` Aneesh Kumar K.V
2026-04-21 11:53 ` Jiri Pirko
2026-04-21 12:10 ` Jason Gunthorpe
2026-04-22 7:51 ` Petr Tesarik
2026-04-22 9:18 ` Aneesh Kumar K.V
2026-04-24 22:55 ` Jason Gunthorpe
2026-04-26 13:05 ` Jason Gunthorpe
2026-05-21 15:35 ` Aneesh Kumar K.V
2026-05-21 17:54 ` Jason Gunthorpe
2026-05-22 4:39 ` Aneesh Kumar K.V
2026-05-22 13:22 ` Jason Gunthorpe [this message]
2026-03-25 19:23 ` [PATCH v5 2/2] dma-buf: heaps: system: add system_cc_shared heap for explicitly " Jiri Pirko
2026-03-27 19:43 ` T.J. Mercier
2026-03-31 15:08 ` Jason Gunthorpe
2026-04-02 12:23 ` Maxime Ripard
2026-04-02 12:56 ` Jiri Pirko
2026-03-27 9:38 ` [PATCH v5 0/2] dma-buf: heaps: system: add an option to allocate explicitly shared/decrypted memory Marek Szyprowski
2026-03-27 12:10 ` Jason Gunthorpe
2026-03-27 19:43 ` T.J. Mercier
2026-04-02 4:41 ` Sumit Semwal
2026-04-02 5:35 ` Marek Szyprowski
2026-04-02 9:52 ` Brian Starkey
2026-04-02 12:02 ` Jason Gunthorpe
2026-04-02 12:58 ` Jiri Pirko
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=20260522132240.GD7702@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=Brian.Starkey@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=ashish.kalra@amd.com \
--cc=benjamin.gaignard@collabora.com \
--cc=catalin.marinas@arm.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jiri@resnulli.us \
--cc=john.allen@amd.com \
--cc=jstultz@google.com \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-media@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=ptesarik@suse.com \
--cc=robin.murphy@arm.com \
--cc=sean.anderson@linux.dev \
--cc=steven.price@arm.com \
--cc=sumit.semwal@linaro.org \
--cc=suravee.suthikulpanit@amd.com \
--cc=suzuki.poulose@arm.com \
--cc=thomas.lendacky@amd.com \
--cc=tjmercier@google.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