Mailing List Archive

On 21/09/2012 05:06, "Bruce Granger" <vivagin@yeah.net> wrote:

> 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)
{
$B!D!D(B
switch ( icr_low & APIC_MODE_MASK )
{
$B!D!D(B
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;
$B!D!D(B
}
$B!D!D(B
I think
> that when we input the shutdown command in GuestOS, xen will first
catch the
> APIC_DM_INIT and then call the
$B!F(Bhvm_vcpu_down(v)$B!G!"!G(Bdomain_shutdown()$B!G(B and so
> on , is that right? If not,
where is the code entrance when shutdown operation
> occurs?



--
View this message in context:


Yes that's about right. Some guests will not re-INIT the VCPUs but will
simply leave them HLTed with interrupts disabled. We also pick up that case
in hvm_hlt().

Once all VCPUs are down, hvm_vcpu_down() dows the domain_shutdown() call,
which then triggers machinery in dom0 to kill off the domain fully. I
described that path in my previous email.

-- Keir

> 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




_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel