From: Bruce Granger <vivagin@yeah.net>
To: xen-devel@lists.xensource.com
Subject: From which place in source code Xen start to deal with the GuestOS shutdown operation?
Date: Thu, 20 Sep 2012 21:06:37 -0700 (PDT) [thread overview]
Message-ID: <1348200397859-5711422.post@n5.nabble.com> (raw)
Hello everyone!
I feel I'm still a new baby though I have been study xen source code for
some days!
When I shutdown GuestOS, I want to get to know how Xen deal with the
operation? I find the code in xen\arch\x86\hvm\vlapic.c, see:
static int vlapic_accept_irq(struct vcpu *v, uint32_t icr_low)
{
……
switch ( icr_low & APIC_MODE_MASK )
{
……
case APIC_DM_INIT:
/* No work on INIT de-assert for P4-type APIC. */
if ( (icr_low & (APIC_INT_LEVELTRIG | APIC_INT_ASSERT)) ==
APIC_INT_LEVELTRIG )
break;
/* Nothing to do if the VCPU is already reset. */
if ( !v->is_initialised )
break;
hvm_vcpu_down(v);
rc = vlapic_schedule_init_sipi_tasklet(v, icr_low);
break;
……
}
……
I think that when we input the shutdown command in GuestOS, xen will first
catch the APIC_DM_INIT and then call the
‘hvm_vcpu_down(v)’、’domain_shutdown()’ and so on , is that right? If not,
where is the code entrance when shutdown operation occurs?
--
View this message in context: http://xen.1045712.n5.nabble.com/From-which-place-in-source-code-Xen-start-to-deal-with-the-GuestOS-shutdown-operation-tp5711422.html
Sent from the Xen - Dev mailing list archive at Nabble.com.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next reply other threads:[~2012-09-21 4:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 4:06 Bruce Granger [this message]
2012-09-21 8:08 ` From which place in source code Xen start to deal with the GuestOS shutdown operation? Keir Fraser
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=1348200397859-5711422.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).