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: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Tue, 04 Oct 2005 13:06:05 -0500
Cc: Jacob Gorm Hansen <jacobg@xxxxxxx>, harry <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Rami Rosen <rosenrami@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, rolf.neugebauer@xxxxxxxxx
Delivery-date: Tue, 04 Oct 2005 18:04:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5d7aca950510041100t17d7ef32g203a397d645ad995@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> <4342BF19.7000904@xxxxxxxxxx> <5d7aca950510041100t17d7ef32g203a397d645ad995@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.6 (X11/20050912)
NAHieu wrote:

If so, I think we can do simply like this to exchange information
between dom0 & domU:

- dom0 watch for @introduceDomain to detect the new domU comes up.
Then dom0 watch for /domU/<device>/{evtchn,grant-ref}
Tools should store their information in /tool/<toolname>/. Otherwise, yeah, it seems sane to me.

Regards,

Anthony Liguori

- domU write evtchn,grant-ref,... to /domU/<device>/{evtchn,grant-ref}
(better doesnt write it outside its home, like in Rolf's example)

- dom0 detect the updates, setup evtchn, then start to notify domU via
this channel. Other data can be written into the share memory (like
grant-ref above) to exchange information at this step.

This way is good (if it works - I will try it myself), since we don't
need to mod xend, which is horrified to many.  Any ideas?

But like Rolf pointed out, this solution is not good incase we want to
save/restore(?)

Thanks.
Hieu

Regards,

Anthony Liguori

So exactly what did you mean?

Thanks.
Hieu

_______________________________________________
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