Hi, Ryan,
A question here. Why does multi-function devices need special
handle on vPCI mode for pcibe/pcife? vPCI mode is just to provide
a full-virtualized PCI hierarchy which already virtualizes busnr/slotnr,
and there's no need to special case the function number. If some rare
driver really has assumption about the multi-function knowledge
about one specific device, just go to "passthrough" mode.
Actually there's even no need to keep a third mode ("slot")
which
makes nothing difference but to provide a virtual function number. We
may keep things simple:
- passthrough to provide real hierarchy, except adding more root
buses
- vPCI to provide virtual hierarchy, with vbus/vslot/vfunction
which have no relationship with real.
Does it sound OK? :-)
Thanks,
Kevins
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
A question here. Why does multi-function devices need special
handle on vPCI mode for pcibe/pcife? vPCI mode is just to provide
a full-virtualized PCI hierarchy which already virtualizes busnr/slotnr,
and there's no need to special case the function number. If some rare
driver really has assumption about the multi-function knowledge
about one specific device, just go to "passthrough" mode.
Actually there's even no need to keep a third mode ("slot")
which
makes nothing difference but to provide a virtual function number. We
may keep things simple:
- passthrough to provide real hierarchy, except adding more root
buses
- vPCI to provide virtual hierarchy, with vbus/vslot/vfunction
which have no relationship with real.
Does it sound OK? :-)
Thanks,
Kevins
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel