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.3-rc1
Date: Tue, 18 Aug 2026 16:43:26 -0600 [thread overview]
Message-ID: <20260818164326.387bb27b@shazbot.org> (raw)
Hi Linus,
The following changes since commit a13c140cc289c0b7b3770bce5b3ad42ab35074aa:
Linux 7.2-rc3 (2026-07-12 14:16:39 -0700)
are available in the Git repository at:
https://github.com/awilliam/linux-vfio.git tags/vfio-v7.3-rc1
for you to fetch changes up to 4e3c1fc8abcb8eff062150b4340fa4569696d645:
vfio/pci: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX (2026-08-13 11:37:30 -0600)
----------------------------------------------------------------
VFIO updates for v7.3-rc1
- Add nv_falcon vfio selftest driver. The Falcon is a general-purpose
microcontroller embedded within NVIDIA GPUs, presenting a relatively
simple DMA programming interface. This adds another selftest target
for vfio-pci with real DMA transfers. (Rubin Du, Alex Williamson)
- Add allocation assertion helpers to vfio selftests and use them to
avoid variable length arrays and the compiler errors they generate.
(Alex Mastro)
- Fix use-after-free hazard where an init path error in MSI support
leaves a stray pointer that can later be reused or double-freed.
(Xiang Mei)
- Fix previous refactor of PCI BAR mappings to honor non_mappable_bars
flag, which otherwise generates a warning when trying to pci_iomap()
a 256TiB BAR on ISM devices on s390. (Farhan Ali)
- Add igb vfio selftest driver. Like nv_falcon, this provides another
target for DMA testing with vfio selftests, but importantly this
driver supports both physical 82576 NICs and the emulation model in
QEMU. This therefore enables a vfio selftest vector with no physical
hardware requirements. (Josh Hilke, Alex Williamson)
- Mark selftest fixture objects __maybe_unused to accommodate builds
with clang -Wunused-but-set-global. (David Matlack)
- Add error recovery for vfio-pci devices on s390x. This expands
devices which expose the existing error eventfd and introduces a
device feature for reporting firmware defined error state
information to the user, allowing recovery through hypervisor
channels. (Farhan Ali)
----------------------------------------------------------------
Alex Mastro (2):
vfio: selftests: Add allocation assert helpers
vfio: selftests: Avoid VLAs
Alex Williamson (2):
vfio: selftests: Add helpers to re-enable interrupts
Merge branch 'slot' of git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci into v7.3/vfio/s390x-pci-error-recovery
David Matlack (1):
selftests: harness: Mark test fixture objects __maybe_unused
Farhan Ali (9):
vfio/pci: Avoid mapping BARs for devices with non-mappable BARs
PCI: Introduce PCI_SLOT_PLACEHOLDER constant for slot_nr placeholder value
PCI: Allow per function PCI slots to fix slot reset on s390
PCI: Avoid saving config space state if inaccessible
PCI: Fail FLR when config space is inaccessible
PCI/MSI: Enable memory decoding before restoring MSI-X messages
s390/pci: Store PCI error information for passthrough devices
vfio-pci/zdev: Add a device feature for error information
vfio/pci: Remove the pcie check for VFIO_PCI_ERR_IRQ_INDEX
Josh Hilke (2):
vfio: selftests: igb: Add driver for Intel 82576 device
vfio: selftests: Retry on EAGAIN during device reset
Rubin Du (4):
vfio: selftests: Add memcpy chunking to vfio_pci_driver_memcpy()
vfio: selftests: Add generic PCI command register helpers
vfio: selftests: Allow drivers without send_msi() support
vfio: selftests: Add NVIDIA Falcon driver for DMA testing
Xiang Mei (1):
vfio/pci: clear vdev->msi_perm after freeing it on init failure
arch/s390/include/asm/pci.h | 32 +
arch/s390/pci/pci.c | 1 +
arch/s390/pci/pci_event.c | 137 ++--
drivers/pci/hotplug/pnv_php.c | 2 +-
drivers/pci/hotplug/rpaphp_slot.c | 2 +-
drivers/pci/msi/msi.c | 10 +
drivers/pci/pci.c | 33 +-
drivers/pci/slot.c | 50 +-
drivers/vfio/pci/vfio_pci_config.c | 1 +
drivers/vfio/pci/vfio_pci_core.c | 13 +-
drivers/vfio/pci/vfio_pci_intrs.c | 3 +-
drivers/vfio/pci/vfio_pci_priv.h | 9 +
drivers/vfio/pci/vfio_pci_zdev.c | 62 +-
include/linux/pci.h | 8 +-
include/uapi/linux/vfio.h | 21 +
include/uapi/linux/vfio_zdev.h | 2 +
tools/testing/selftests/kselftest_harness.h | 2 +-
.../selftests/vfio/lib/drivers/igb/e1000_82575.h | 1 +
.../selftests/vfio/lib/drivers/igb/e1000_defines.h | 1 +
.../selftests/vfio/lib/drivers/igb/e1000_regs.h | 1 +
tools/testing/selftests/vfio/lib/drivers/igb/igb.c | 585 +++++++++++++++
.../selftests/vfio/lib/drivers/nv_falcon/hw.h | 352 +++++++++
.../vfio/lib/drivers/nv_falcon/nv_falcon.c | 783 +++++++++++++++++++++
.../selftests/vfio/lib/include/libvfio/assert.h | 18 +
.../vfio/lib/include/libvfio/vfio_pci_device.h | 29 +
tools/testing/selftests/vfio/lib/iommu.c | 12 +-
tools/testing/selftests/vfio/lib/iova_allocator.c | 4 +-
tools/testing/selftests/vfio/lib/libvfio.mk | 3 +
tools/testing/selftests/vfio/lib/sysfs.c | 3 +-
tools/testing/selftests/vfio/lib/vfio_pci_device.c | 74 +-
tools/testing/selftests/vfio/lib/vfio_pci_driver.c | 22 +-
.../vfio/vfio_pci_device_init_perf_test.c | 4 +-
.../testing/selftests/vfio/vfio_pci_driver_test.c | 57 +-
33 files changed, 2196 insertions(+), 141 deletions(-)
create mode 120000 tools/testing/selftests/vfio/lib/drivers/igb/e1000_82575.h
create mode 120000 tools/testing/selftests/vfio/lib/drivers/igb/e1000_defines.h
create mode 120000 tools/testing/selftests/vfio/lib/drivers/igb/e1000_regs.h
create mode 100644 tools/testing/selftests/vfio/lib/drivers/igb/igb.c
create mode 100644 tools/testing/selftests/vfio/lib/drivers/nv_falcon/hw.h
create mode 100644 tools/testing/selftests/vfio/lib/drivers/nv_falcon/nv_falcon.c
reply other threads:[~2026-08-18 22:43 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=20260818164326.387bb27b@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