From: Bruce Granger <vivagin@yeah.net>
To: xen-devel@lists.xensource.com
Subject: Re: How could Xen know a certain GuestOS have already shutdown?
Date: Mon, 24 Sep 2012 06:12:59 -0700 (PDT) [thread overview]
Message-ID: <1348492379003-5711476.post@n5.nabble.com> (raw)
In-Reply-To: <1348197814609-5711421.post@n5.nabble.com>
It's my honor to receive your answer! Thanks very much!
I have learned much more under your guidance,but I still have a little
question!
I've traced the VIRQ_DOM_EXC which send from Xen to Dom0 and picked up by
xenstored which fires the @releaseDomain watch when a GuestOS start to
shutdown.
Here, I still have two questions.
First, I haven't found anything useful in the archives about 'releaseDomain
watch'.What is the called '@releaseDomain' ? what's the use of it?
Second,I think that VIRQ_DOM_EXC is the signal used for communicate between
hypervisor and Dom0. I talked that with my parterner, we think that when
shutdown occurs, GuestOS will first get in touch with hypervisor ,then cause
the communication between Xen and Dom0 by VIRQ_DOM_EXC,is that right? What
we also want to know is when shutdown operation occurs in GuestOS, how
GuestOS communicate with the hypervisor first? Is there any signal or
somehow event delivery?
Could you tell me more about that?
Thanks a lot!
--
View this message in context: http://xen.1045712.n5.nabble.com/Xen-devel-How-could-Xen-know-a-certain-GuestOS-have-already-shutdown-tp5711421p5711476.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
next prev parent reply other threads:[~2012-09-24 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 3:23 How could Xen know a certain GuestOS have already shutdown? Bruce Granger
2012-09-21 8:06 ` Keir Fraser
2012-09-24 13:12 ` Bruce Granger [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-09-24 17:09 Bruce Granger
2012-09-25 8:22 ` Ian Campbell
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=1348492379003-5711476.post@n5.nabble.com \
--to=vivagin@yeah.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).