RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed

["Xu, Anthony" <anthony.xu@xxxxxxxxx>]

>-----Original Message-----
>From: Kouya SHIMURA [mailto:kouya@xxxxxxxxxxxxxx]
>Sent: 2006年10月11日 14:27
>To: Xu, Anthony
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed
>
>Hi Anthony,
>
>I think that vmx_final_setup_guest() is called asynchronously.
>Because the secondary vcpus are waken by IPI, not control panel.
>Actually we can observe the following log message asynchronously.
>(XEN) arch_boot_vcpu: vcpu 1 awaken 00000000046bc180!
You are right at this point.
>
>vmx_relinquish_vcpu_resources() is called after sched_destroy_domain().
>If the scheduler stops vcpus completely in sched_destroy_domain(),
>it might be OK. But it seems to be up to scheduler.

I'm not sure about this, 
But, if vcpus are not completely stopped before calling 
vmx_relinquish_vcpu_resources,
That's a big issue; vcpus may access some memories which have been freed and 
may be
used by other guys.


Keir,

When free_vcpu_struct() is called, is it guaranteed that this vcpu is stopped 
completely?

Thanks,
Anthony

_______________________________________________
Xen-ia64-devel mailing list
Xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-ia64-devel