[Xen-devel] Broken PCI device passthrough, after XSA-302 fix?

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

Hi,

I have a multi-function PCI device, behind a PCI bridge, that normally
I assign to a single domain. But now it fails with:

(XEN) [VT-D]d14: 0000:04:00.0 owned by d0!<G><0>assign 0000:05:00.0 to dom14 
failed (-22)

This is Xen 4.8.5 + XSA patches. It started happening after some update
during last few months, not really sure which one.

I guess it is because quarantine feature, so initial ownership of
0000:05:00.0 is different than the bridge it is connected to.
I'm not sure if relevant for this case, but I also set
pcidev->rdm_policy = LIBXL_RDM_RESERVE_POLICY_RELAXED.

Booting with iommu=no-quarantine helps. Note I do not use `xl
pci-assignable-add` command, only bind the device to the pciback driver
in dom0.

Relevant part of lspci and lspci -t:

00:00.0 Host bridge: Intel Corporation 4th Gen Core Processor DRAM Controller 
(rev 06)
..
00:1c.3 PCI bridge: Intel Corporation 9 Series Chipset Family PCI Express Root 
Port 4 (rev d0)
..
04:00.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 41)
05:00.0 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.1 USB controller: NEC Corporation OHCI USB Controller (rev 43)
05:00.2 USB controller: NEC Corporation uPD72010x USB 2.0 Controller (rev 04)

-[0000:00]-+-00.0
..
           +-1c.3-[04-05]----00.0-[05]--+-00.0
           |                            +-00.1
           |                            \-00.2


-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

Attachment: signature.asc
Description: PGP signature

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