Hi, > > I'd say the risk for regressions is rather low, though, given that it > > only affects configurations that would fail PCI resource allocation > > today. Or am I missing something? > > > > In any case, the PCIe spec is clear about this: I/O space is optional, > > and we need to incorporate this into the generic code at *some* point. > > It makes no sense for every individual platform to keep adding these > > hacks. > Do you know how Linux handles this? > Can Linux allocate resource for PCI(E) devices? How does it deal with the IO > type?
Yes. Details depend a bit on the specific configuration, but in general linux will try assign io address space to pcie root ports and devices plugged into those ports. A failure is not considered fatal though. A more common case than the pci root bridge not supporting io address space at all is having more than 16 pcie root ports. Given io bride windows are 1k in size and we have 16k total there is simply not enough io address space in that case, so some of the root ports stay without io and linux is fine with that. > Why changing the MdeModulePkg's IncompatiblePciDevice driver can avoid > stalling the patch series? > I feel it's enough to just change the OvmfPkg version. It's not much of a problem for ovmf even without such an update, typically the devices used with microvm don't have io bars in the first place. Also note that without this series pcie devices are not supported at all on microvm, so not supporting all devices initially wouldn't be a regression. I'll look into it in any case. take care, Gerd -=-=-=-=-=-=-=-=-=-=-=- Groups.io Links: You receive all messages sent to this group. View/Reply Online (#89390): https://edk2.groups.io/g/devel/message/89390 Mute This Topic: https://groups.io/mt/90623478/21656 Group Owner: devel+ow...@edk2.groups.io Unsubscribe: https://edk2.groups.io/g/devel/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
