[Xen-devel] [PATCH v2 0/4] Fix PCI passthrough for HVM with stubdomain

[Marek Marczykowski-Górecki <marmarek@xxxxxxxxxxxxxxxxxxxxxx>]

This is yet another attempt to upstream a set of PCI passthrough related fixed
carried in Qubes OS packages for a long time already.
Some of them were already discussed previously, see another thread with the
same subject back in October 2016.

As for "xen/x86: Allow stubdom access to irq created for msi" patch, this is
only one part of fixing MSI with QEMU in stubdomain. The other part is allowing
stubdomain to actually enable MSI in PCI config space.  QEMU does that through
pcifront/back connected to the stubdomain (see
hw/xen/xen_pt_msi.c:msi_msix_enable()), but pciback by default refuse
write to that register.
Easy, less safe solution: enable permissive mode for the device.
Safer solution - enable access to this register for stubdomain only:
 - pciback patch: 
https://github.com/QubesOS/qubes-linux-kernel/blob/master/0015-xen-pciback-add-attribute-to-allow-MSI-enable-flag-w.patch
 - libxl patch: 
https://github.com/QubesOS/qubes-vmm-xen/blob/xen-4.8/patch-stubdom-allow-msi-enable.patch

The whole story:
https://www.qubes-os.org/news/2017/10/18/msi-support/

Any other ideas? Which one is preferred upstream?

Changes in v2:
 - new "xen/x86: Allow stubdom access to irq created for msi" patch
 - applied review comments from v1

Marek Marczykowski-Górecki (3):
  libxl: do not attach xen-pciback to HVM domain, if stubdomain is in use
  libxl: attach PCI device to qemu only after setting pciback/pcifront
  libxl: don't try to manipulate json config for stubdomain

Simon Gaiser (1):
  xen/x86: Allow stubdom access to irq created for msi.

 tools/libxl/libxl_pci.c | 37 ++++++++++++++++++++++++++-----------
 xen/arch/x86/irq.c      | 23 +++++++++++++++++++++++
 xen/arch/x86/physdev.c  |  9 +++++++++
 3 files changed, 58 insertions(+), 11 deletions(-)

base-commit: 93a62c544e20ba9e141e411bbaae3d65259d13a3
-- 
git-series 0.9.1

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel