[v1,0/3,RFC] get real IOMMU information from VFIO IOMMU

Message

Pierre Morel Jan. 9, 2019, 12:41 p.m. UTC

In the Z-Architecture, the IOMMU information may change on a device
basis.
until this patch series we used hardcoded values to define the
IOMMU aperture we provide to the guest during PCI enumeration.

Let's ask the host about the IOMMU specific configuration using
VFIO capabilities.

NOTES:
1- You will need the according Linux patch to test this.

2- I am really not happy to add S390 dedicated code in the
   VFIO common code, as do SPAPR, but I did not find a better
   solution.
   Any idea?

Pierre Morel (3):
  vfio: Linux header placeholder
  vfio/pci: Get real IOMMU information from container
  s390x/pci: Reporting the host aperture to the guest

 hw/s390x/s390-pci-bus.c       |  2 +-
 hw/s390x/s390-pci-bus.h       |  3 ++
 hw/s390x/s390-pci-inst.c      | 20 ++++++++++--
 hw/vfio/common.c              | 75 +++++++++++++++++++++++++++++++++----------
 include/hw/vfio/vfio-common.h |  3 ++
 linux-headers/linux/vfio.h    | 65 +++++++++++++++++++++++++++++++++++--
 6 files changed, 144 insertions(+), 24 deletions(-)

Comments

[e-mail] Jan. 13, 2019, 2:29 p.m. UTC | #1

Patchew URL: https://patchew.org/QEMU/[e-mail]/



Hi,

This series failed the docker-quick@centos7 build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.

=== TEST SCRIPT BEGIN ===
#!/bin/bash
time make docker-test-quick@centos7 SHOW_ENV=1 J=8
=== TEST SCRIPT END ===




The full log is available at
http://patchew.org/logs/[e-mail]/testing.docker-quick@centos7/?type=message.
---
Email generated automatically by Patchew [http://patchew.org/].
Please send your feedback to [e-mail]