WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] xl: Support backend domain ID for disks

Daniel De Graaf writes ("Re: [Xen-devel] [PATCH] xl: Support backend domain ID 
for disks"):
> If we change the stat() so that it's only done on types that require a file,
> then all that is required is to create a "remote-phy" type that does not do
> the stat locally. This type would also avoid trying to fill in nodes like
> "physical-device" that are derived from the stat(), leaving those to be
> filled in by the backend domain.

Right, that seems like a good approach.

> > I think that in the New World Order, a driver domain should be told
> > the pdev_path and left to get on with it.  So something in the driver
> > domain needs to watch xenstore.  Perhaps a BSD-style backendd ?
> 
> That would make the most sense. Linux does get events when this part of
> xenstore is updated, so it may be possible to fire off the needed events
> from udev/hotplug depending on what can be picked up there.

Right.

Ian.

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