From: "Michael S. Tsirkin" <mst@redhat.com>
To: Shameer Kolothum <skolothumtho@nvidia.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org,
eric.auger@redhat.com, alex@shazbot.org, clg@redhat.com,
cohuck@redhat.com, nicolinc@nvidia.com, nathanc@nvidia.com,
mochs@nvidia.com, jgg@nvidia.com, jonathan.cameron@huawei.com,
zhenzhong.duan@intel.com, vivek.kasireddy@intel.com,
kjaju@nvidia.com
Subject: Re: [PATCH v4 0/3] vfio: Add DMABUF support for PCI BAR regions
Date: Wed, 21 Jan 2026 07:36:33 -0500 [thread overview]
Message-ID: <20260121073625-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260121114111.34045-1-skolothumtho@nvidia.com>
On Wed, Jan 21, 2026 at 11:41:08AM +0000, Shameer Kolothum wrote:
> Hi,
>
> Linux now provides a VFIO dmabuf exporter to expose PCI BAR memory for P2P
> use cases. This adds support for vfio devices to create a dmabuf for
> each mapped BAR region.
>
> Changes from v3:
> https://lore.kernel.org/qemu-devel/20260116092950.15796-1-skolothumtho@nvidia.com/
>
> - Folded in patch #2 to linux-headers update to avoid bisect failure
> due to build error.
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
> The dmabuf support was sanity tested on an NVIDIA grace paltform.
>
> Please take a look and let me know.
>
> Thanks,
> Shameer
>
> Nicolin Chen (1):
> hw/vfio/region: Create dmabuf for PCI BAR per region
>
> Shameer Kolothum (2):
> linux-headers: Update to Linux v6.19-rc1
> hw/vfio: Add helper to retrieve device feature
>
> hw/net/virtio-net.c | 11 +-
> hw/vfio/container.c | 2 +-
> hw/vfio/device.c | 9 ++
> hw/vfio/listener.c | 4 +-
> hw/vfio/region.c | 65 +++++++++-
> hw/vfio/trace-events | 1 +
> include/hw/vfio/vfio-device.h | 3 +
> include/standard-headers/drm/drm_fourcc.h | 25 ++--
> include/standard-headers/linux/ethtool.h | 5 +
> .../linux/input-event-codes.h | 14 ++-
> include/standard-headers/linux/pci_regs.h | 89 ++++++++++++++
> include/standard-headers/linux/virtio_net.h | 3 +-
> include/standard-headers/linux/virtio_pci.h | 2 +-
> linux-headers/asm-arm64/kvm.h | 2 +-
> linux-headers/asm-arm64/unistd_64.h | 1 +
> linux-headers/asm-generic/unistd.h | 4 +-
> linux-headers/asm-loongarch/kvm.h | 1 +
> linux-headers/asm-loongarch/unistd.h | 6 +
> linux-headers/asm-loongarch/unistd_64.h | 1 +
> linux-headers/asm-mips/unistd_n32.h | 1 +
> linux-headers/asm-mips/unistd_n64.h | 1 +
> linux-headers/asm-mips/unistd_o32.h | 1 +
> linux-headers/asm-powerpc/unistd_32.h | 1 +
> linux-headers/asm-powerpc/unistd_64.h | 1 +
> linux-headers/asm-riscv/kvm.h | 3 +
> linux-headers/asm-riscv/unistd_32.h | 1 +
> linux-headers/asm-riscv/unistd_64.h | 1 +
> linux-headers/asm-s390/bitsperlong.h | 4 -
> linux-headers/asm-s390/unistd.h | 4 -
> linux-headers/asm-s390/unistd_64.h | 9 +-
> linux-headers/asm-x86/kvm.h | 1 +
> linux-headers/asm-x86/unistd_32.h | 1 +
> linux-headers/asm-x86/unistd_64.h | 1 +
> linux-headers/asm-x86/unistd_x32.h | 1 +
> linux-headers/linux/iommufd.h | 10 ++
> linux-headers/linux/kvm.h | 11 ++
> linux-headers/linux/mshv.h | 116 +++++++++++++++++-
> linux-headers/linux/psp-sev.h | 66 ++++++----
> linux-headers/linux/vfio.h | 28 +++++
> 39 files changed, 450 insertions(+), 60 deletions(-)
>
> --
> 2.43.0
next prev parent reply other threads:[~2026-01-21 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 11:41 [PATCH v4 0/3] vfio: Add DMABUF support for PCI BAR regions Shameer Kolothum
2026-01-21 11:41 ` [PATCH v4 1/3] linux-headers: Update to Linux v6.19-rc1 Shameer Kolothum
2026-01-21 14:00 ` Cédric Le Goater
2026-01-21 14:21 ` Peter Maydell
2026-01-21 17:12 ` Jason Gunthorpe
2026-01-23 14:26 ` Cédric Le Goater
2026-01-21 11:41 ` [PATCH v4 2/3] hw/vfio: Add helper to retrieve device feature Shameer Kolothum
2026-01-21 11:41 ` [PATCH v4 3/3] hw/vfio/region: Create dmabuf for PCI BAR per region Shameer Kolothum
2026-01-21 12:36 ` Michael S. Tsirkin [this message]
2026-01-21 12:49 ` [PATCH v4 0/3] vfio: Add DMABUF support for PCI BAR regions Eric Auger
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=20260121073625-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=alex@shazbot.org \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=eric.auger@redhat.com \
--cc=jgg@nvidia.com \
--cc=jonathan.cameron@huawei.com \
--cc=kjaju@nvidia.com \
--cc=mochs@nvidia.com \
--cc=nathanc@nvidia.com \
--cc=nicolinc@nvidia.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=skolothumtho@nvidia.com \
--cc=vivek.kasireddy@intel.com \
--cc=zhenzhong.duan@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.