[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] multi-function devices on vPCI bus


  • To: "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Ryan Wilson" <hap9@xxxxxxxxxxxxxx>
  • From: "Tian, Kevin" <kevin.tian@xxxxxxxxx>
  • Date: Mon, 6 Nov 2006 17:34:08 +0800
  • Delivery-date: Mon, 06 Nov 2006 07:24:49 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccBhrVcO7V0Kr3BQymhOtNfbrbtzA==
  • Thread-topic: multi-function devices on vPCI bus

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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.