search for: pci_find_upstream_pcie_bridg

...e (bus << 8 | devfn), like a >> >> s/the/they/ >> >> Did you learn about this empirically? Intel spec? I wonder if there's >> some way to derive this from the PCIe specs. > > It's in the current intel-iommu logic, pretty much anywhere it uses > pci_find_upstream_pcie_bridge() it follows that up with a pci_is_pcie() > check. If it's PCIe, it uses a traditional PCIe-to-PCI bridge ID. If > it's a legacy PCI bridge it uses the bridge ID itself. > > static int > domain_context_mapping(struct dmar_domain *domain, struct pci_dev *pdev, >...

Hi Pierre, thanks for your reply. I am using kernel 3.10.0-123.8.1.el7.x86_64. The kernel modul used after nodedev-detach is vfio-pci This is the output of lspci -vv after I did a virsh nodedev-detatch pci_0000_02_00_0 02:00.0 Ethernet controller: PLX Technology, Inc. Device 235e Subsystem: PLX Technology, Inc. Device 235e Control: I/O- Mem- BusMaster- SpecCycle- MemWINV-