[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Kouya SHIMURA" <kouya@xxxxxxxxxxxxxx>
  • From: "Xu, Anthony" <anthony.xu@xxxxxxxxx>
  • Date: Wed, 11 Oct 2006 13:47:45 +0800
  • Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 10 Oct 2006 22:48:19 -0700
  • List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
  • Thread-index: Acbs74HbfFAC6E2WR3qQWX1nmv4OtgACF+WA
  • Thread-topic: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed

>From: Kouya SHIMURA [mailto:kouya@xxxxxxxxxxxxxx]
>Sent: 2006年10月11日 12:41
>To: Xu, Anthony
>Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
>Subject: RE: [Xen-ia64-devel] [PATCH] Xen panics when domvti is destroyed
>Hi Anthony,
>
>Thanks for your comment.
>If it is safe that vmx_reliquish_vcpu_resouces(vcpu) is called
>before the vcpu is booted, your modification looks better.
>
>I'm afraid of the race condition between vmx_final_setup_guest()
>and vmx_relinquish_vcpu_resources().
>Supposing such a condition, we might have to use some lock in order to
>prevent memory leak. How do you think?

I see your point,
In this situation, vmx_final_setup_guest() and vmx_relinquish_vcpu_resources()
are called by control panel, they should not be called serially not 
simultaneously.


Anthony

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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.