WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

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

To: "Kouya SHIMURA" <kouya@xxxxxxxxxxxxxx>, "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed
From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
Date: Wed, 11 Oct 2006 15:34:00 +0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 11 Oct 2006 00:34:33 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acbs/kv++4t7caymQ1qydw46xK/VmwACASqg
Thread-topic: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed
>-----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

<Prev in Thread] Current Thread [Next in Thread>