42a945317b
- kvm-virtio-iommu-Fix-64kB-host-page-size-VFIO-device-ass.patch [bz#2211609 bz#2211634] - kvm-virtio-iommu-Rework-the-traces-in-virtio_iommu_set_p.patch [bz#2211609 bz#2211634] - kvm-vfio-pci-add-support-for-VF-token.patch [bz#2192818] - kvm-vfio-migration-Skip-log_sync-during-migration-SETUP-.patch [bz#2192818] - kvm-vfio-pci-Static-Resizable-BAR-capability.patch [bz#2192818] - kvm-vfio-pci-Fix-a-use-after-free-issue.patch [bz#2192818] - kvm-util-vfio-helpers-Use-g_file_read_link.patch [bz#2192818] - kvm-migration-Make-all-functions-check-have-the-same-for.patch [bz#2192818] - kvm-migration-Move-migration_properties-to-options.c.patch [bz#2192818] - kvm-migration-Add-switchover-ack-capability.patch [bz#2192818] - kvm-migration-Implement-switchover-ack-logic.patch [bz#2192818] - kvm-migration-Enable-switchover-ack-capability.patch [bz#2192818] - kvm-vfio-migration-Refactor-vfio_save_block-to-return-sa.patch [bz#2192818] - kvm-vfio-migration-Store-VFIO-migration-flags-in-VFIOMig.patch [bz#2192818] - kvm-vfio-migration-Add-VFIO-migration-pre-copy-support.patch [bz#2192818] - kvm-vfio-migration-Add-support-for-switchover-ack-capabi.patch [bz#2192818] - kvm-vfio-Implement-a-common-device-info-helper.patch [bz#2192818] - kvm-hw-vfio-pci-quirks-Support-alternate-offset-for-GPUD.patch [bz#2192818] - kvm-vfio-pci-Call-vfio_prepare_kvm_msi_virq_batch-in-MSI.patch [bz#2192818] - kvm-vfio-migration-Reset-bytes_transferred-properly.patch [bz#2192818] - kvm-vfio-migration-Make-VFIO-migration-non-experimental.patch [bz#2192818] - kvm-vfio-pci-Fix-a-segfault-in-vfio_realize.patch [bz#2192818] - kvm-vfio-pci-Free-leaked-timer-in-vfio_realize-error-pat.patch [bz#2192818] - kvm-hw-vfio-pci-quirks-Sanitize-capability-pointer.patch [bz#2192818] - kvm-vfio-pci-Disable-INTx-in-vfio_realize-error-path.patch [bz#2192818] - kvm-vfio-migration-Change-vIOMMU-blocker-from-global-to-.patch [bz#2192818] - kvm-vfio-migration-Free-resources-when-vfio_migration_re.patch [bz#2192818] - kvm-vfio-migration-Remove-print-of-Migration-disabled.patch [bz#2192818] - kvm-vfio-migration-Return-bool-type-for-vfio_migration_r.patch [bz#2192818] - kvm-vfio-Fix-null-pointer-dereference-bug-in-vfio_bars_f.patch [bz#2192818] - kvm-pc-bios-s390-ccw-Makefile-Use-z-noexecstack-to-silen.patch [bz#2220866] - kvm-pc-bios-s390-ccw-Fix-indentation-in-start.S.patch [bz#2220866] - kvm-pc-bios-s390-ccw-Provide-space-for-initial-stack-fra.patch [bz#2220866] - kvm-pc-bios-s390-ccw-Don-t-use-__bss_start-with-the-larl.patch [bz#2220866] - kvm-ui-Fix-pixel-colour-channel-order-for-PNG-screenshot.patch [bz#2222579] - kvm-block-blkio-fix-module_block.py-parsing.patch [bz#2213317] - kvm-Fix-virtio-blk-vhost-vdpa-typo-in-spec-file.patch [bz#2213317] - Resolves: bz#2211609 (With virtio-iommu and vfio-pci, qemu reports "warning: virtio-iommu page mask 0xfffffffffffff000 does not match 0x40201000") - Resolves: bz#2211634 ([aarch64] With virtio-iommu and vfio-pci, qemu coredump when host using kernel-64k package) - Resolves: bz#2192818 ([VFIO LM] Live migration) - Resolves: bz#2220866 (Misaligned symbol for s390-ccw image during qemu-kvm build) - Resolves: bz#2222579 (PNG screendump doesn't save screen correctly) - Resolves: bz#2213317 (Enable libblkio-based block drivers in QEMU)
111 lines
4.1 KiB
Diff
111 lines
4.1 KiB
Diff
From dd38230a0a375fb8427fa106ff79562e56c51b6c Mon Sep 17 00:00:00 2001
|
|
From: =?UTF-8?q?C=C3=A9dric=20Le=20Goater?= <clg@redhat.com>
|
|
Date: Wed, 12 Jul 2023 17:46:57 +0200
|
|
Subject: [PATCH 18/37] hw/vfio/pci-quirks: Support alternate offset for
|
|
GPUDirect Cliques
|
|
MIME-Version: 1.0
|
|
Content-Type: text/plain; charset=UTF-8
|
|
Content-Transfer-Encoding: 8bit
|
|
|
|
RH-Author: Cédric Le Goater <clg@redhat.com>
|
|
RH-MergeRequest: 179: vfio: live migration support
|
|
RH-Bugzilla: 2192818
|
|
RH-Acked-by: Eric Auger <eric.auger@redhat.com>
|
|
RH-Acked-by: Miroslav Rezanina <mrezanin@redhat.com>
|
|
RH-Commit: [16/28] 9befb7c9adaeb58e9d0b49686cf54b751c742832 (clegoate/qemu-kvm-c9s)
|
|
|
|
Bugzilla: https://bugzilla.redhat.com/2192818
|
|
|
|
commit f6b30c1984f7
|
|
Author: Alex Williamson <alex.williamson@redhat.com>
|
|
Date: Thu Jun 8 12:05:07 2023 -0600
|
|
|
|
hw/vfio/pci-quirks: Support alternate offset for GPUDirect Cliques
|
|
|
|
NVIDIA Turing and newer GPUs implement the MSI-X capability at the offset
|
|
previously reserved for use by hypervisors to implement the GPUDirect
|
|
Cliques capability. A revised specification provides an alternate
|
|
location. Add a config space walk to the quirk to check for conflicts,
|
|
allowing us to fall back to the new location or generate an error at the
|
|
quirk setup rather than when the real conflicting capability is added
|
|
should there be no available location.
|
|
|
|
Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
|
|
Reviewed-by: Cédric Le Goater <clg@redhat.com>
|
|
Signed-off-by: Cédric Le Goater <clg@redhat.com>
|
|
|
|
Signed-off-by: Cédric Le Goater <clg@redhat.com>
|
|
---
|
|
hw/vfio/pci-quirks.c | 41 ++++++++++++++++++++++++++++++++++++++++-
|
|
1 file changed, 40 insertions(+), 1 deletion(-)
|
|
|
|
diff --git a/hw/vfio/pci-quirks.c b/hw/vfio/pci-quirks.c
|
|
index f0147a050a..0ed2fcd531 100644
|
|
--- a/hw/vfio/pci-quirks.c
|
|
+++ b/hw/vfio/pci-quirks.c
|
|
@@ -1490,6 +1490,9 @@ void vfio_setup_resetfn_quirk(VFIOPCIDevice *vdev)
|
|
* +---------------------------------+---------------------------------+
|
|
*
|
|
* https://lists.gnu.org/archive/html/qemu-devel/2017-08/pdfUda5iEpgOS.pdf
|
|
+ *
|
|
+ * Specification for Turning and later GPU architectures:
|
|
+ * https://lists.gnu.org/archive/html/qemu-devel/2023-06/pdf142OR4O4c2.pdf
|
|
*/
|
|
static void get_nv_gpudirect_clique_id(Object *obj, Visitor *v,
|
|
const char *name, void *opaque,
|
|
@@ -1530,7 +1533,9 @@ const PropertyInfo qdev_prop_nv_gpudirect_clique = {
|
|
static int vfio_add_nv_gpudirect_cap(VFIOPCIDevice *vdev, Error **errp)
|
|
{
|
|
PCIDevice *pdev = &vdev->pdev;
|
|
- int ret, pos = 0xC8;
|
|
+ int ret, pos;
|
|
+ bool c8_conflict = false, d4_conflict = false;
|
|
+ uint8_t tmp;
|
|
|
|
if (vdev->nv_gpudirect_clique == 0xFF) {
|
|
return 0;
|
|
@@ -1547,6 +1552,40 @@ static int vfio_add_nv_gpudirect_cap(VFIOPCIDevice *vdev, Error **errp)
|
|
return -EINVAL;
|
|
}
|
|
|
|
+ /*
|
|
+ * Per the updated specification above, it's recommended to use offset
|
|
+ * D4h for Turing and later GPU architectures due to a conflict of the
|
|
+ * MSI-X capability at C8h. We don't know how to determine the GPU
|
|
+ * architecture, instead we walk the capability chain to mark conflicts
|
|
+ * and choose one or error based on the result.
|
|
+ *
|
|
+ * NB. Cap list head in pdev->config is already cleared, read from device.
|
|
+ */
|
|
+ ret = pread(vdev->vbasedev.fd, &tmp, 1,
|
|
+ vdev->config_offset + PCI_CAPABILITY_LIST);
|
|
+ if (ret != 1 || !tmp) {
|
|
+ error_setg(errp, "NVIDIA GPUDirect Clique ID: error getting cap list");
|
|
+ return -EINVAL;
|
|
+ }
|
|
+
|
|
+ do {
|
|
+ if (tmp == 0xC8) {
|
|
+ c8_conflict = true;
|
|
+ } else if (tmp == 0xD4) {
|
|
+ d4_conflict = true;
|
|
+ }
|
|
+ tmp = pdev->config[tmp + PCI_CAP_LIST_NEXT];
|
|
+ } while (tmp);
|
|
+
|
|
+ if (!c8_conflict) {
|
|
+ pos = 0xC8;
|
|
+ } else if (!d4_conflict) {
|
|
+ pos = 0xD4;
|
|
+ } else {
|
|
+ error_setg(errp, "NVIDIA GPUDirect Clique ID: invalid config space");
|
|
+ return -EINVAL;
|
|
+ }
|
|
+
|
|
ret = pci_add_capability(pdev, PCI_CAP_ID_VNDR, pos, 8, errp);
|
|
if (ret < 0) {
|
|
error_prepend(errp, "Failed to add NVIDIA GPUDirect cap: ");
|
|
--
|
|
2.39.3
|
|
|