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] xenstore documentation

Sorry, I think that should have been

domainpath/device/device_class/device_id/transaction_stuff_here for the
front_end.

Also, see correction below:

On Tue, 2005-10-04 at 13:42 +0100, harry wrote:
> If you look at writeDetails in
> tools/python/xen/xend/server/DevController.py you'll see the
> transactions which cause the back and front ends to get probed.
> 
> The transactions contain extra fields as provided by the derived class
> specific to the device type and are written into the store in the
> locations constructed in the frontendPath and backendPath functions in
> DevController.py.  These paths contain the

> device id - nope.

device_class

> string as specified
> when you registered your xenbus drivers.
> 
> Looking at the current code, it looks like
> domainpath/backend/device_class/frontend_uuid/device_id/transaction_stuff_here
> for the back-end and and
> domainpath/device_id/transaction_stuff_here
> for the front-end.
> 
> HTH
> 
> Harry.
> 
> On Tue, 2005-10-04 at 14:20 +0200, Jacob Gorm Hansen wrote:
> > On 10/4/05, Rami Rosen <rosenrami@xxxxxxxxx> wrote:
> > > Hello ,
> > >
> > >  I had written some pages which I had inserted into XenWiki this morning.
> > >  It is in http://wiki.xensource.com/xenwiki/XenIntro.
> > 
> > Thanks a lot for this work. I suppose my main problem right now is
> > finding out why the backend probe function is never called. Does
> > anyone know what the tools in dom0 have to do to trigger the backend
> > driver probe function?
> > 
> > Thanks,
> > Jacob
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@xxxxxxxxxxxxxxxxxxx
> > http://lists.xensource.com/xen-devel
> > 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
> 


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