From: Anthony Liguori <aliguori@us.ibm.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
Subject: Re: xenstore documentation
Date: Tue, 04 Oct 2005 13:06:05 -0500 [thread overview]
Message-ID: <4342C48D.4040706@us.ibm.com> (raw)
In-Reply-To: <5d7aca950510041100t17d7ef32g203a397d645ad995@mail.gmail.com>
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
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
next prev parent reply other threads:[~2005-10-04 18:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-03 17:03 xenstore documentation Jacob Gorm Hansen
2005-10-04 6:27 ` Rami Rosen
2005-10-04 12:20 ` Jacob Gorm Hansen
2005-10-04 12:42 ` harry
2005-10-04 12:48 ` harry
2005-10-04 12:56 ` Jacob Gorm Hansen
2005-10-04 13:17 ` harry
2005-10-04 13:31 ` Jacob Gorm Hansen
2005-10-04 15:05 ` Anthony Liguori
2005-10-04 15:28 ` Nivedita Singhvi
2005-10-04 15:46 ` Anthony Liguori
2005-10-04 15:33 ` Jacob Gorm Hansen
2005-10-04 15:55 ` Anthony Liguori
2005-10-04 18:13 ` Jacob Gorm Hansen
2005-10-04 18:20 ` Anthony Liguori
2005-10-04 22:12 ` Jacob Gorm Hansen
2005-10-05 17:17 ` Anthony Liguori
2005-10-05 17:22 ` Jacob Gorm Hansen
2005-10-04 12:55 ` NAHieu
2005-10-04 13:25 ` harry
2005-10-04 14:42 ` Rolf Neugebauer
2005-10-04 17:24 ` NAHieu
2005-10-04 17:36 ` Rolf Neugebauer
2005-10-04 17:42 ` Anthony Liguori
2005-10-04 18:00 ` NAHieu
2005-10-04 18:06 ` Anthony Liguori [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 21:47 Neugebauer, Rolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4342C48D.4040706@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=harry@hebutterworth.freeserve.co.uk \
--cc=jacobg@diku.dk \
--cc=nahieu@gmail.com \
--cc=rolf.neugebauer@intel.com \
--cc=rosenrami@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.