On 2018-04-26 17:53, [email protected] wrote: > On Cavium ThunderX there are PCI devices and multiple PCI domains, each > with a set of buses and MMIO areas. > DeviceTree can be used to identify all those. > > I see a flag pci_is_virtual is true on Arm. > But I am not sure I fully understand the implications. > > In theory, we should add multi-domain support to allow proper device > probing here correct ? >
Look at http://lists.infradead.org/pipermail/linux-arm-kernel/2018-April/573481.html e.g. Will likely become PCI: Enable PCI_DOMAINS along with generic PCI host controller This controller is often instantiated by hypervisors, and they may add multiple of them or add them in addition to a physical host controller like the Jailhouse hypervisor is doing. Therefore allow for multiple domains so that we can handle them all. Signed-off-by: Jan Kiszka <[email protected]> --- drivers/pci/host/Kconfig | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pci/host/Kconfig b/drivers/pci/host/Kconfig index 0d0177ce436c..3d25b35bb5ab 100644 --- a/drivers/pci/host/Kconfig +++ b/drivers/pci/host/Kconfig @@ -68,6 +68,7 @@ config PCI_HOST_GENERIC depends on (ARM || ARM64) && OF select PCI_HOST_COMMON select IRQ_DOMAIN + select PCI_DOMAINS help Say Y here if you want to support a simple generic PCI host controller, such as the one emulated by kvmtool. We do use interception of a physical host controller as well, but only on the Seattle. The whole series (http://lists.infradead.org/pipermail/linux-arm-kernel/2018-April/573492.html) might be of interest for you. For studies, or maybe you can even support reviews. Oh, and I'm still looking for someone to help me getting http://lists.infradead.org/pipermail/linux-arm-kernel/2018-January/555415.html in. :) Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "Jailhouse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
