|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [PATCH v15 4/5] xen/arm: translate virtual PCI bus topology for guests
Hi Stewart, On 17/05/2024 18:06, Stewart Hildebrand wrote: From: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx> There are three originators for the PCI configuration space access: 1. The domain that owns physical host bridge: MMIO handlers are there so we can update vPCI register handlers with the values written by the hardware domain, e.g. physical view of the registers vs guest's view on the configuration space. 2. Guest access to the passed through PCI devices: we need to properly map virtual bus topology to the physical one, e.g. pass the configuration space access to the corresponding physical devices. 3. Emulated host PCI bridge access. It doesn't exist in the physical topology, e.g. it can't be mapped to some physical host bridge. So, all access to the host bridge itself needs to be trapped and emulated. Signed-off-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@xxxxxxxx> Signed-off-by: Volodymyr Babchuk <volodymyr_babchuk@xxxxxxxx> Signed-off-by: Stewart Hildebrand <stewart.hildebrand@xxxxxxx> With one remark below, for Arm: Acked-by: Julien Grall <jgrall@xxxxxxxxxx> [...]
(This doesn't need to be addressed now)I see that we have other places with for_each_pdev() in the vCPI. So are we expecting the list to be smallish? If not, then we may want to consider reworking the datastructure or put a limit on the number of PCI devices assigned.
Cheers, -- Julien Grall
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |