On 11/13/20 4:51 PM, Jan Beulich wrote: > On 13.11.2020 15:44, Oleksandr Andrushchenko wrote: >> On 11/13/20 4:38 PM, Jan Beulich wrote: >>> On 13.11.2020 15:32, Oleksandr Andrushchenko wrote: >>>> On 11/13/20 4:23 PM, Jan Beulich wrote: >>>>> Earlier on I didn't say you should get this to work, only >>>>> that I think the general logic around what you add shouldn't make >>>>> things more arch specific than they really should be. That said, >>>>> something similar to the above should still be doable on x86, >>>>> utilizing struct pci_seg's bus2bridge[]. There ought to be >>>>> DEV_TYPE_PCI_HOST_BRIDGE entries there, albeit a number of them >>>>> (provided by the CPUs themselves rather than the chipset) aren't >>>>> really host bridges for the purposes you're after. >>>> You mean I can still use DEV_TYPE_PCI_HOST_BRIDGE as a marker >>>> >>>> while trying to detect what I need? >>> I'm afraid I don't understand what marker you're thinking about >>> here. >> I mean that when I go over bus2bridge entries, should I only work with >> >> those who have DEV_TYPE_PCI_HOST_BRIDGE? > Well, if you're after host bridges - yes. Ok, I'll try to see what I can do about it. > > Jan
Thank you, Oleksandr
