[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Is: 'basic pci bridge and root device support. 'Was:Re: Discussion about virtual iommu support for Xen guest
> For HVMLite, there is specifically no qemu, and we need something which > can function when we want PCI Passthrough to work. I am quite confident > that the correct solution here is to have a basic host bridge/root port > implementation in Xen (as we already have 80% of this already), at which > point we don't need any qemu interaction for PCI Passthough at all, even > for HVM guests. Could you expand on this a bit? I am asking b/c some time ago I wrote in Xen code to construct a full view of the bridges->devices (and various in branching) so that I could renumber the bus values and its devices (expand them) on bridges. This was solely done so that I could use SR-IOV devices on non-SR-IOV capable BIOSes. I am wondering how much of the basic functionality (enumeration, keeping track, etc) could be worked in this 'basic host bridge/root port' implementation idea of yours. Attaching the patches. Attachment:
0001-pci-On-PCI-dump-device-keyhandler-include-Device-and.patch Attachment:
0002-DEBUG-Include-upstream-bridge-information.patch Attachment:
0003-xen-pci-assign-buses-Renumber-the-bus-if-there-is-a-.patch Attachment:
0004-pci-assign-buses-Suspend-resume-the-console-device-a.patch Attachment:
0005-pci-assign-busses-Add-Mellenox.patch _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |