Hi Roger, On 14/08/17 15:28, Roger Pau Monne wrote:
This functionality is going to reside in vpci.c (and the corresponding vpci.h header), and should be arch-agnostic. The handlers introduced in this patch setup the basic functionality required in order to trap accesses to the PCI config space, and allow decoding the address and finding the corresponding handler that should handle the access (although no handlers are implemented).
If I understand correctly this patch, the virtual BDF will always correspond to the physical BDF. Is that right? If so, would you mind to explain why such restriction?
Cheers, -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
