Ingo Molnar wrote:
> * Eric W. Biederman <[email protected]> wrote:
> 
>> Not finding an upstream pcie_bridge and then concluding we are a
>> pcie device seems bogus. 
>> 

If device is pcie, pci_find_upstream_pcie_bridge() will return NULL. For root 
complex integrated device, it won't find upstream bridge, and also return NULL. 
What's more, pcie device and root complex integrated device will be handled as 
the same way to set sid, so I mix them here. But it also returns NULL for 
busted hardware. I think no parent bus can be considered Root Complex 
integrated device, right? If so, I think can handle it as follows:

        ...
        if (dev->is_pcie || !dev->bus->parent) {
                set_irte_sid(...);
                return 0;
        }

        bridge = pci_find_upstream_pcie_bridge(dev);
        if (bridge) {
                if (bridge->is_pcie) /* PCIE-to-PCI/PCIx bridge */
                        set_irte_sid(...);
                else /* legacy PCI bridge */
                        set_irte_sid(..);
        }

        return 0;

>> Why if we do have an upstream pcie bridge do we only want to do a
>> bus range verification instead of checking just for the bus
>>> devfn?
>> 
>> The legacy PCI case seems even stranger.

Why? If a PCI device isn't connected to a PCIe bridge, it should be a legacy 
bridge.

Regards,
Weidong

> 
> Good points. Would be nice to get an ack from the PCI folks to make
> sure these bits are sane.
> 

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to