From: Alex Williamson <alex@shazbot.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: alex@shazbot.org, "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] VFIO updates for v7.2-rc1
Date: Mon, 15 Jun 2026 16:38:49 -0600 [thread overview]
Message-ID: <20260615163849.5b6ac84c@shazbot.org> (raw)
Hi Linus,
The following changes since commit 5200f5f493f79f14bbdc349e402a40dfb32f23c8:
Linux 7.1-rc4 (2026-05-17 13:59:58 -0700)
are available in the Git repository at:
https://github.com/awilliam/linux-vfio.git tags/vfio-v7.2-rc1
for you to fetch changes up to 785562e31dbcd85ca583cf58c446e63aa8a5af08:
vfio: selftests: Ensure libvfio output dirs are always created (2026-06-12 10:25:44 -0600)
----------------------------------------------------------------
VFIO updates for v7.2-rc1
- Fix out-of-tree vfio selftest builds with make O=. (Jason Gunthorpe)
- Allow vfio selftests to build when ARCH=x86 is used for 64-bit x86
builds. (David Matlack)
- Tighten vfio selftest infrastructure with stricter builds, safer
path handling, sysfs helpers, and reusable device/VF-token setup.
Build on that to add the SR-IOV UAPI selftest across supported
IOMMU modes. (Raghavendra Rao Ananta)
- Conclude earlier vfio PCI BAR work already taken as v7.1 fixes by
replacing vfio_pci_core_setup_barmap() and direct barmap[] access
with vfio_pci_core_get_iomap(). Fix resulting sparse warnings.
(Matt Evans)
- Simplify hisi_acc vfio-pci variant driver device-info reads by
using the mailbox's new direct command-based read helper.
(Weili Qian)
- Avoid duplicate reset handling in the Xe vfio-pci variant driver
reset-done path. (GuoHan Zhao)
- Resolve a lockdep circular dependency splat by tracking active
VFs with a private sriov_active flag rather than calling
pci_num_vf() under memory_lock. (Raghavendra Rao Ananta)
- Add CXL DVSEC-based readiness polling for Blackwell-Next in the
nvgrace-gpu vfio-pci variant driver, including interruptible,
lockless waits to support worst case spec defined timeouts.
(Ankit Agrawal)
- Prevent vfio_mig_get_next_state() from spinning forever on blocked
migration state transition. (Junrui Luo)
- Fix a qat vfio variant driver migration resume race by taking the
migration file lock before boundary checks. (Giovanni Cabiddu)
- Add explicit dependencies between vfio selftest output object files
and output directories to ensure directories are always created.
(David Matlack)
----------------------------------------------------------------
Ankit Agrawal (1):
vfio/nvgrace-gpu: Add Blackwell-Next GPU readiness check via CXL DVSEC
David Matlack (2):
vfio: selftests: Allow builds when ARCH=x86
vfio: selftests: Ensure libvfio output dirs are always created
Giovanni Cabiddu (1):
vfio/qat: fix f_pos race in qat_vf_resume_write()
GuoHan Zhao (1):
vfio/xe: avoid duplicate reset in xe_vfio_pci_reset_done
Jason Gunthorpe (1):
vfio: selftests: Fix out-of-tree build with make O=
Junrui Luo (1):
vfio: prevent infinite loop in vfio_mig_get_next_state() on blocked arc
Matt Evans (2):
vfio/pci: Replace vfio_pci_core_setup_barmap() with vfio_pci_core_get_iomap()
vfio/pci: Fix sparse warning in vfio_pci_core_get_iomap()
Raghavendra Rao Ananta (9):
vfio: selftests: Add -Wall and -Werror to the Makefile
vfio: selftests: Introduce snprintf_assert()
vfio: selftests: Introduce a sysfs lib
vfio: selftests: Extend container/iommufd setup for passing vf_token
vfio: selftests: Expose more vfio_pci_device functions
vfio: selftests: Add helper to set/override a vf_token
vfio: selftests: Add helpers to alloc/free vfio_pci_device
vfio: selftests: Add tests to validate SR-IOV UAPI
vfio/pci: Use a private flag to prevent power state change with VFs
Weili Qian (1):
hisi_acc_vfio_pci: simplify the command for reading device information
drivers/vfio/pci/hisilicon/hisi_acc_vfio_pci.c | 39 +---
drivers/vfio/pci/nvgrace-gpu/main.c | 180 +++++++++++++++--
drivers/vfio/pci/qat/main.c | 16 +-
drivers/vfio/pci/vfio_pci_core.c | 28 ++-
drivers/vfio/pci/vfio_pci_dmabuf.c | 2 +-
drivers/vfio/pci/vfio_pci_rdwr.c | 30 +--
drivers/vfio/pci/virtio/legacy_io.c | 13 +-
drivers/vfio/pci/xe/main.c | 2 -
drivers/vfio/vfio_main.c | 3 +-
include/linux/vfio_pci_core.h | 21 +-
include/uapi/linux/pci_regs.h | 1 +
tools/testing/selftests/vfio/Makefile | 11 +-
tools/testing/selftests/vfio/lib/include/libvfio.h | 1 +
.../selftests/vfio/lib/include/libvfio/assert.h | 5 +
.../selftests/vfio/lib/include/libvfio/sysfs.h | 12 ++
.../vfio/lib/include/libvfio/vfio_pci_device.h | 11 ++
tools/testing/selftests/vfio/lib/libvfio.mk | 7 +-
tools/testing/selftests/vfio/lib/sysfs.c | 150 ++++++++++++++
tools/testing/selftests/vfio/lib/vfio_pci_device.c | 157 +++++++++++----
.../testing/selftests/vfio/vfio_dma_mapping_test.c | 6 +-
.../testing/selftests/vfio/vfio_pci_device_test.c | 21 +-
.../selftests/vfio/vfio_pci_sriov_uapi_test.c | 217 +++++++++++++++++++++
22 files changed, 775 insertions(+), 158 deletions(-)
create mode 100644 tools/testing/selftests/vfio/lib/include/libvfio/sysfs.h
create mode 100644 tools/testing/selftests/vfio/lib/sysfs.c
create mode 100644 tools/testing/selftests/vfio/vfio_pci_sriov_uapi_test.c
reply other threads:[~2026-06-15 22:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260615163849.5b6ac84c@shazbot.org \
--to=alex@shazbot.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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