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: harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xenstore documentation
From: NAHieu <nahieu@xxxxxxxxx>
Date: Tue, 4 Oct 2005 21:55:57 +0900
Cc: Rami Rosen <rosenrami@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, Jacob Gorm Hansen <jacobg@xxxxxxx>
Delivery-date: Tue, 04 Oct 2005 12:53:31 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=hzemt8gn1pbYvFoPeaN0tak1HMMXK10URwkXgiLQHlZe2g7L5RhSkzEwE3ICnRNQ8kxZFZQODjzC2RHHRcoUl9fntzMHntg7l3IZ831gyo9O6w3dFSZnwZjilYZBjVlcooffMYoohfM0ipAG19n3PTMhjIU1IggSOoBtjMx5D2s=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1128429737.30221.12.camel@xxxxxxxxxxxxxxxxxxxxx>
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>
Reply-to: NAHieu <nahieu@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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?

I have the same problem here: I am struggling on the first simple
backend/frontend driver, and I cannot figure out why probe functions
in the frontend is not called.

Jacob, would you please share some of your experiences if you make
your code run successfully?

Many thanks.
Hieu.

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