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

Re: [Xen-devel] [PATCH] x86/nestedhvm: properly clean up after failure to set up all vCPU-s


  • To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Wed, 23 Jan 2013 15:17:03 +0000
  • Delivery-date: Wed, 23 Jan 2013 15:17:42 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac35fLKG4BkaI5AWdUqQm25S7q+nWQ==
  • Thread-topic: [Xen-devel] [PATCH] x86/nestedhvm: properly clean up after failure to set up all vCPU-s

On 23/01/2013 14:24, "Jan Beulich" <JBeulich@xxxxxxxx> wrote:

> This implies that the individual destroy functions will have to remain
> capable of being called for a vCPU that the corresponding init function
> was never run on.
> 
> Once at it, also clean up some inefficiencies in the corresponding
> parameter validation code.
> 
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Acked-by: Keir Fraser <keir@xxxxxxx>

But doubtless should have a nestedhvm maintainer ack too.



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


 


Rackspace

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