From: "Christian König" <christian.koenig@amd.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: "Sumit Semwal" <sumit.semwal@linaro.org>,
"Alex Deucher" <alexander.deucher@amd.com>,
"David Airlie" <airlied@gmail.com>,
"Simona Vetter" <simona@ffwll.ch>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Gurchetan Singh" <gurchetansingh@chromium.org>,
"Chia-I Wu" <olvaffe@gmail.com>,
"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
"Maxime Ripard" <mripard@kernel.org>,
"Thomas Zimmermann" <tzimmermann@suse.de>,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"Kevin Tian" <kevin.tian@intel.com>,
"Joerg Roedel" <joro@8bytes.org>, "Will Deacon" <will@kernel.org>,
"Robin Murphy" <robin.murphy@arm.com>,
"Felix Kuehling" <Felix.Kuehling@amd.com>,
"Alex Williamson" <alex@shazbot.org>,
"Ankit Agrawal" <ankita@nvidia.com>,
"Vivek Kasireddy" <vivek.kasireddy@intel.com>,
linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org,
linaro-mm-sig@lists.linaro.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, virtualization@lists.linux.dev,
intel-xe@lists.freedesktop.org, linux-rdma@vger.kernel.org,
iommu@lists.linux.dev, kvm@vger.kernel.org
Subject: Re: [PATCH v7 0/8] dma-buf: Use revoke mechanism to invalidate shared buffers
Date: Wed, 4 Feb 2026 09:54:13 +0100 [thread overview]
Message-ID: <6d5c392b-596b-4341-9992-aa4b26001804@amd.com> (raw)
In-Reply-To: <20260204081630.GA6771@unreal>
On 2/4/26 09:16, Leon Romanovsky wrote:
> On Mon, Feb 02, 2026 at 06:04:25PM +0200, Leon Romanovsky wrote:
>> On Sat, Jan 31, 2026 at 07:34:10AM +0200, Leon Romanovsky wrote:
>>> Changelog:
>>> v7:
>>
>> <...>
>>
>>> Leon Romanovsky (8):
>>> dma-buf: Rename .move_notify() callback to a clearer identifier
>>> dma-buf: Rename dma_buf_move_notify() to dma_buf_invalidate_mappings()
>>> dma-buf: Always build with DMABUF_MOVE_NOTIFY
>>> vfio: Wait for dma-buf invalidation to complete
>>> dma-buf: Make .invalidate_mapping() truly optional
>>> dma-buf: Add dma_buf_attach_revocable()
>>> vfio: Permit VFIO to work with pinned importers
>>> iommufd: Add dma_buf_pin()
>>>
>>> drivers/dma-buf/Kconfig | 12 -----
>>> drivers/dma-buf/dma-buf.c | 69 ++++++++++++++++++++-----
>>> drivers/gpu/drm/amd/amdgpu/amdgpu_dma_buf.c | 14 ++---
>>> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 2 +-
>>> drivers/gpu/drm/amd/amdkfd/Kconfig | 2 +-
>>> drivers/gpu/drm/virtio/virtgpu_prime.c | 2 +-
>>> drivers/gpu/drm/xe/tests/xe_dma_buf.c | 7 ++-
>>> drivers/gpu/drm/xe/xe_bo.c | 2 +-
>>> drivers/gpu/drm/xe/xe_dma_buf.c | 14 ++---
>>> drivers/infiniband/core/umem_dmabuf.c | 13 -----
>>> drivers/infiniband/hw/mlx5/mr.c | 2 +-
>>> drivers/iommu/iommufd/pages.c | 11 +++-
>>> drivers/iommu/iommufd/selftest.c | 2 +-
>>> drivers/vfio/pci/vfio_pci_dmabuf.c | 80 ++++++++++++++++++++++-------
>>> include/linux/dma-buf.h | 17 +++---
>>> 15 files changed, 153 insertions(+), 96 deletions(-)
>>
>> Christian,
>>
>> Given the ongoing discussion around patch v5, I'm a bit unclear on the
>> current state. Is the series ready for merging, or do you need me to
>> rework anything further?
>
> Christian,
>
> Let's not miss the merge window for work that is already ready.
Mhm, sounds like AMDs mail servers never send my last mail out.
As far as I can see all patches have an reviewed-by, I also gave an rb on patch #6 (should that mail never got out as well). The discussion on patch v5 is just orthogonal I think, the handling was there even completely before this patch set.
For upstreaming as long as the VFIO and infiniband folks don't object I would like to take that through the drm-misc branch (like every other DMA-buf change).
So as long as nobody objects I can push that today, but I can't promise that Dave/Linus will take it for the 6.20 window.
Regards,
Christian.
>
> Thanks
>
>>
>> Thanks
>>
next prev parent reply other threads:[~2026-02-04 8:54 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-31 5:34 [PATCH v7 0/8] dma-buf: Use revoke mechanism to invalidate shared buffers Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 1/8] dma-buf: Rename .move_notify() callback to a clearer identifier Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 2/8] dma-buf: Rename dma_buf_move_notify() to dma_buf_invalidate_mappings() Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 3/8] dma-buf: Always build with DMABUF_MOVE_NOTIFY Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 4/8] vfio: Wait for dma-buf invalidation to complete Leon Romanovsky
2026-02-04 14:47 ` Alex Williamson
2026-01-31 5:34 ` [PATCH v7 5/8] dma-buf: Make .invalidate_mapping() truly optional Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 6/8] dma-buf: Add dma_buf_attach_revocable() Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 7/8] vfio: Permit VFIO to work with pinned importers Leon Romanovsky
2026-02-04 16:21 ` Christian König
2026-02-04 16:55 ` Jason Gunthorpe
2026-02-04 16:56 ` Alex Williamson
2026-02-05 9:43 ` Christian König
2026-02-05 12:19 ` Leon Romanovsky
2026-02-05 14:21 ` Jason Gunthorpe
2026-02-05 14:28 ` Christian König
2026-02-05 14:41 ` Alex Williamson
2026-02-05 14:58 ` Jason Gunthorpe
2026-02-04 17:41 ` Leon Romanovsky
2026-01-31 5:34 ` [PATCH v7 8/8] iommufd: Add dma_buf_pin() Leon Romanovsky
2026-02-02 16:04 ` [PATCH v7 0/8] dma-buf: Use revoke mechanism to invalidate shared buffers Leon Romanovsky
2026-02-04 8:16 ` Leon Romanovsky
2026-02-04 8:54 ` Christian König [this message]
2026-02-04 11:47 ` Leon Romanovsky
2026-02-04 14:49 ` Alex Williamson
2026-02-04 13:35 ` Jason Gunthorpe
2026-02-04 8:56 ` Maxime Ripard
2026-02-04 11:52 ` Leon Romanovsky
2026-02-04 12:01 ` Maxime Ripard
2026-02-04 12:13 ` Leon Romanovsky
2026-02-04 13:44 ` Maxime Ripard
2026-02-04 13:56 ` Jason Gunthorpe
2026-02-04 15:54 ` Leon Romanovsky
2026-02-05 9:09 ` Maxime Ripard
2026-02-17 8:02 ` Leon Romanovsky
2026-02-17 9:52 ` Christian König
2026-02-17 13:34 ` Leon Romanovsky
2026-02-23 18:55 ` Christian König
2026-02-24 10:31 ` Leon Romanovsky
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=6d5c392b-596b-4341-9992-aa4b26001804@amd.com \
--to=christian.koenig@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=airlied@gmail.com \
--cc=alex@shazbot.org \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ankita@nvidia.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gurchetansingh@chromium.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linaro-mm-sig@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=olvaffe@gmail.com \
--cc=robin.murphy@arm.com \
--cc=rodrigo.vivi@intel.com \
--cc=simona@ffwll.ch \
--cc=sumit.semwal@linaro.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=virtualization@lists.linux.dev \
--cc=vivek.kasireddy@intel.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