From mboxrd@z Thu Jan  1 00:00:00 1970
From: Anthony Liguori <aliguori@us.ibm.com>
Subject: Re: xenstore documentation
Date: Tue, 04 Oct 2005 13:06:05 -0500
Message-ID: <4342C48D.4040706@us.ibm.com>
References: <e08041f30510031003p6c4911b8n22dbf10bd1a1997f@mail.gmail.com>	
	<ae5426fb0510032327r4589aaerc4d279825dca0ad8@mail.gmail.com>	
	<e08041f30510040520g53e96456xa7d93168fa8cdf90@mail.gmail.com>	
	<1128429737.30221.12.camel@localhost.localdomain>	
	<5d7aca950510040555k19e8fb71kb74deff11c344451@mail.gmail.com>	
	<1128432335.30221.33.camel@localhost.localdomain>	
	<1128436946.29007.6.camel@wyvis.research.intel-research.net>	
	<5d7aca950510041024l7d82d7d7h536e0e3aa0ff8728@mail.gmail.com>	
	<4342BF19.7000904@us.ibm.com>
	<5d7aca950510041100t17d7ef32g203a397d645ad995@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <5d7aca950510041100t17d7ef32g203a397d645ad995@mail.gmail.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: NAHieu <nahieu@gmail.com>
Cc: Jacob Gorm Hansen <jacobg@diku.dk>, harry <harry@hebutterworth.freeserve.co.uk>, Rami Rosen <rosenrami@gmail.com>, xen-devel@lists.xensource.com, rolf.neugebauer@intel.com
List-Id: xen-devel@lists.xenproject.org

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@lists.xensource.com
>>>http://lists.xensource.com/xen-devel
>>>
>>>
>>>
>>>      
>>>
>>    
>>
>
>  
>