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

To: NAHieu <nahieu@xxxxxxxxx>
Subject: Re: [Xen-devel] xenstore documentation
From: Rolf Neugebauer <rolf.neugebauer@xxxxxxxxx>
Date: Tue, 04 Oct 2005 18:36:30 +0100
Cc: Rami Rosen <rosenrami@xxxxxxxxx>, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Jacob Gorm Hansen <jacobg@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, rolf.neugebauer@xxxxxxxxx
Delivery-date: Tue, 04 Oct 2005 17:34:15 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5d7aca950510041024l7d82d7d7h536e0e3aa0ff8728@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <e08041f30510031003p6c4911b8n22dbf10bd1a1997f@xxxxxxxxxxxxxx> <ae5426fb0510032327r4589aaerc4d279825dca0ad8@xxxxxxxxxxxxxx> <e08041f30510040520g53e96456xa7d93168fa8cdf90@xxxxxxxxxxxxxx> <1128429737.30221.12.camel@xxxxxxxxxxxxxxxxxxxxx> <5d7aca950510040555k19e8fb71kb74deff11c344451@xxxxxxxxxxxxxx> <1128432335.30221.33.camel@xxxxxxxxxxxxxxxxxxxxx> <1128436946.29007.6.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <5d7aca950510041024l7d82d7d7h536e0e3aa0ff8728@xxxxxxxxxxxxxx>
Reply-to: rolf.neugebauer@xxxxxxxxx
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2005-10-04 at 18:24, NAHieu wrote:
> On 10/4/05, Rolf Neugebauer <rolf.neugebauer@xxxxxxxxx> wrote:
> > On Tue, 2005-10-04 at 14:25, harry wrote:
> > > On Tue, 2005-10-04 at 21:55 +0900, NAHieu wrote:
> > > > On 10/4/05, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> 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 string as 
> > > > > specified
> > > > > when you registered your xenbus drivers.
> > > > >
> > > >
> > > > Does that mean if I want to write a new split device, I must patch
> > > > xend to let it aware of the new type of device?
> > >
> > > Yes.  You have to add a new class in python/xen/xend/server (see
> > > blkif.py as an example) and then hook this class into xend in
> > > XendDomainInfo.py and xm/create.py to get the config parameters passed
> > > correctly.
> >
> > or no ;) depending on what you want to do. so for example if you only
> > ever have one backend in the system then you "could" store that under a
> > well known name in the store and the frontends can simply read that.
> > you'll also need a place for the BE to watch for FE updates in a similar
> > fashion.
> >
> 
> Rolf, I am really suprised here: how can BE watch for FE updates? BE
> and FE are in different domain, so they cannot access each other
> xenstore tree. (??)
> 
> So exactly what did you mean?

so, you BE could set up:
/foobar/backend/domid = 2
/foobar/frontends          <- watch on this

then FE looks up /foobar/backend/domid
setup its end of eventchannel + grant for shared page
then creates:
/foobar/frontends/<domid>/fe_port
/foobar/frontends/<domid>/grant_ref

BE watch fires, reads port and GR and finalises device channel set up

Seems to work for me.

Rolf


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