Re: [Xen-devel] [RFC] Use device path to assign devices to guest domain

[Yuji Shimada <shimada-yxb@xxxxxxxxxxxxxxx>]

On Thu, 26 Feb 2009 10:00:30 +0000
David Edmondson <dme@xxxxxxx> wrote:

> 
> On 26 Feb 2009, at 8:40am, Yuji Shimada wrote:
> > I hope developers give me some comments.
> 
> I don't really have an opinion about what happens on Linux.
> 
> The current Solaris IO domain work uses the BDF derived naming for PCI  
> devices in domain specifications. We have been discussing using  
> Solaris device paths (such as /pci@0,0/pci8086,3605@2/pci8086,3500@0/ 
> pci8086,3518@2/pci108e,4836@0,1) instead, as it would simplify various  
> parts of our implementation and administration model.

Thank you for your reply.

I'm sorry, I don't know much about Solaris device path.
My device path doesn't use bus# but ACPI's _HID, _UID, device# and
function#. Therefore, even if a new device is added, device path
remains unchanged. For your reference, I attached our example figure.

My device path is similar to EFI's one. So my RFC suits fine on x86 and
IA64 architecture.

My RFC keeps current Xen's SBDF assignment. So you can add Solaris
device path if you need to do.

Thanks,
--
Yuji Shimada

Attachment: assignment_by_devicepath.PNG
Description: PNG image

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel