From: "Cédric Le Goater" <clg@redhat.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>, qemu-devel@nongnu.org
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Akihiko Odaki" <odaki@rsg.ci.i.u-tokyo.ac.jp>,
"Dmitry Osipenko" <dmitry.osipenko@collabora.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Leon Romanovsky" <leon@kernel.org>,
"Leon Romanovsky" <leonro@nvidia.com>,
"Jason Gunthorpe" <jgg@nvidia.com>,
"Dongwon Kim" <dongwon.kim@intel.com>
Subject: Re: [PATCH v1 0/7] vfio: Implement VFIO_DEVICE_FEATURE_DMA_BUF and use it in virtio-gpu
Date: Mon, 6 Oct 2025 17:28:50 +0200 [thread overview]
Message-ID: <6aae1d93-f531-4550-95e5-07f91b432aba@redhat.com> (raw)
In-Reply-To: <20251003234138.85820-1-vivek.kasireddy@intel.com>
Vivek,
On 10/4/25 01:35, Vivek Kasireddy wrote:
> The virtio-gpu driver running in the Guest VM can create Guest blob
> resources (by importing dmabufs) that are backed by System RAM. This
> is made possible by making use of memfd memory backend and udmabuf
> driver on the Host side. However, in order to create Guest blobs
> that are backed by vfio-pci device regions (which happens when
> virtio-gpu imports dmabufs from devices that have local memory such
> as dGPU VFs), we have to implement VFIO_DEVICE_FEATURE_DMA_BUF and
> leverage it in virtio-gpu.
>
> So, while creating the blobs we use memory_region_is_ram_device() to
> figure out if the blob is backed by memfd or a vfio-pci device. If
> it is determined that the blob is backed by vfio-pci device region,
> instead of calling into udmabuf driver to create dmabuf we would
> now call into vfio-pci driver to have a dmabuf created on the Host.
>
> RFC -> v1:
> - Create the CPU mapping using vfio device fd if the dmabuf exporter
> (vfio-pci) does not provide mmap() support (Akihiko)
> - Log a warning with LOG_GUEST_ERROR instead of warn_report() when
> dmabuf cannot be created using Guest provided addresses (Akihiko)
> - Use address_space_translate() instead of gpa2hva() to obtain the
> Host addresses (Akihiko)
> - Rearrange the patches and improve the commit messages (Akihiko)
> - Fix compilation error when VFIO is not enabled (Alex)
> - Add a new helper to obtain VFIO region index from memory region
> - Move vfio_device_create_dmabuf() to hw/vfio/device.c
>
> Tested with an SRIOV enabled Intel dGPU by running Gnome Wayland
Could you please be more precise on the HW ?
> (in the VM) and Qemu with the following (relevant) parameters:
> -device vfio-pci,host=0000:03:00.1
> -device virtio-vga,max_outputs=1,xres=1920,yres=1080,blob=true
> -display gtk,gl=on
>
> Associated vfio-pci kernel driver series:
> https://lore.kernel.org/dri-devel/cover.1754311439.git.leon@kernel.org/
> Associated virtio-gpu kernel driver series (merged):
> https://lore.kernel.org/dri-devel/20241126031643.3490496-1-vivek.kasireddy@intel.com/
>
> ---
> Cc: Marc-André Lureau <marcandre.lureau@redhat.com>
> Cc: Alex Bennée <alex.bennee@linaro.org>
> Cc: Akihiko Odaki <odaki@rsg.ci.i.u-tokyo.ac.jp>
> Cc: Dmitry Osipenko <dmitry.osipenko@collabora.com>
> Cc: Alex Williamson <alex.williamson@redhat.com>
> Cc: Cédric Le Goater <clg@redhat.com>
> Cc: Leon Romanovsky <leon@kernel.org>
> Cc: Leon Romanovsky <leonro@nvidia.com>
> Cc: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Dongwon Kim <dongwon.kim@intel.com>
>
> Vivek Kasireddy (7):
> virtio-gpu: Recreate the resource's dmabuf if new backing is attached
> virtio-gpu: Don't rely on res->blob to identify blob resources
> virtio-gpu: Find hva for Guest's DMA addr associated with a ram device
> vfio/region: Add a helper to get region index from memory region
> linux-headers: Update vfio.h to include VFIO_DEVICE_FEATURE_DMA_BUF
> vfio/device: Add support for VFIO_DEVICE_FEATURE_DMA_BUF
> virtio-gpu-udmabuf: Create dmabuf for blobs associated with VFIO
> devices
>
> hw/display/Kconfig | 5 ++
> hw/display/virtio-gpu-udmabuf.c | 143 ++++++++++++++++++++++++++++++--
> hw/display/virtio-gpu.c | 53 +++++++++---
> hw/vfio/device.c | 43 ++++++++++
> hw/vfio/region.c | 14 ++++
> include/hw/vfio/vfio-device.h | 5 ++
> linux-headers/linux/vfio.h | 25 ++++++
> 7 files changed, 270 insertions(+), 18 deletions(-)
>
Please cc: Alex and I on all patches.
Thanks,
C.
next prev parent reply other threads:[~2025-10-06 15:30 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 23:35 [PATCH v1 0/7] vfio: Implement VFIO_DEVICE_FEATURE_DMA_BUF and use it in virtio-gpu Vivek Kasireddy
2025-10-03 23:35 ` [PATCH v1 1/7] virtio-gpu: Recreate the resource's dmabuf if new backing is attached Vivek Kasireddy
2025-10-14 4:36 ` Akihiko Odaki
2025-10-15 4:56 ` Kasireddy, Vivek
2025-10-03 23:35 ` [PATCH v1 2/7] virtio-gpu: Don't rely on res->blob to identify blob resources Vivek Kasireddy
2025-10-10 4:19 ` Akihiko Odaki
2025-10-13 6:54 ` Kasireddy, Vivek
2025-10-14 4:15 ` Akihiko Odaki
2025-10-15 5:07 ` Kasireddy, Vivek
2025-10-15 6:11 ` Akihiko Odaki
2025-10-15 12:08 ` Akihiko Odaki
2025-10-16 5:41 ` Kasireddy, Vivek
2025-10-16 6:50 ` Akihiko Odaki
2025-10-17 5:58 ` Kasireddy, Vivek
2025-10-17 12:18 ` Akihiko Odaki
2025-10-20 6:40 ` Kasireddy, Vivek
2025-10-21 4:19 ` Akihiko Odaki
2025-10-22 5:10 ` Kasireddy, Vivek
2025-10-23 5:22 ` Akihiko Odaki
2025-10-24 6:08 ` Kasireddy, Vivek
2025-10-16 5:36 ` Kasireddy, Vivek
2025-10-03 23:35 ` [PATCH v1 3/7] virtio-gpu: Find hva for Guest's DMA addr associated with a ram device Vivek Kasireddy
2025-10-14 4:38 ` Akihiko Odaki
2025-10-15 4:55 ` Kasireddy, Vivek
2025-10-03 23:35 ` [PATCH v1 4/7] vfio/region: Add a helper to get region index from memory region Vivek Kasireddy
2025-10-06 8:26 ` Cédric Le Goater
2025-10-07 4:50 ` Kasireddy, Vivek
2025-10-07 9:05 ` Cédric Le Goater
2025-10-03 23:35 ` [PATCH v1 5/7] linux-headers: Update vfio.h to include VFIO_DEVICE_FEATURE_DMA_BUF Vivek Kasireddy
2025-10-03 23:35 ` [PATCH v1 6/7] vfio/device: Add support for VFIO_DEVICE_FEATURE_DMA_BUF Vivek Kasireddy
2025-10-06 8:24 ` Cédric Le Goater
2025-10-07 4:48 ` Kasireddy, Vivek
2025-10-03 23:36 ` [PATCH v1 7/7] virtio-gpu-udmabuf: Create dmabuf for blobs associated with VFIO devices Vivek Kasireddy
2025-10-06 15:59 ` Cédric Le Goater
2025-10-07 4:53 ` Kasireddy, Vivek
2025-10-07 6:51 ` Cédric Le Goater
2025-10-10 4:53 ` Akihiko Odaki
2025-10-13 7:00 ` Kasireddy, Vivek
2025-10-14 4:49 ` Akihiko Odaki
2025-10-15 4:54 ` Kasireddy, Vivek
2025-10-15 5:06 ` Akihiko Odaki
2025-10-16 5:31 ` Kasireddy, Vivek
2025-10-06 15:28 ` Cédric Le Goater [this message]
2025-10-07 4:51 ` [PATCH v1 0/7] vfio: Implement VFIO_DEVICE_FEATURE_DMA_BUF and use it in virtio-gpu Kasireddy, Vivek
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=6aae1d93-f531-4550-95e5-07f91b432aba@redhat.com \
--to=clg@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=alex.williamson@redhat.com \
--cc=dmitry.osipenko@collabora.com \
--cc=dongwon.kim@intel.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=marcandre.lureau@redhat.com \
--cc=odaki@rsg.ci.i.u-tokyo.ac.jp \
--cc=qemu-devel@nongnu.org \
--cc=vivek.kasireddy@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;
as well as URLs for NNTP newsgroup(s).