[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>
  • From: Keir Fraser <keir@xxxxxxx>
  • Date: Wed, 23 Jan 2013 16:46:11 +0000
  • Cc: xen-devel <xen-devel@xxxxxxxxxxxxx>
  • Delivery-date: Wed, 23 Jan 2013 16:46:33 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>
  • Thread-index: Ac35iSYuFEhZpjlgYEKnYIg/FZAXRQ==
  • Thread-topic: [Xen-devel] [PATCH] x86/nestedhvm: properly clean up after failure to set up all vCPU-s

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

>>>> On 23.01.13 at 16:17, Keir Fraser <keir@xxxxxxx> wrote:
>> 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.
> Whoever that is. This was actually the first patch for XSA-35, so
> would have gone in without people seeing this who didn't already
> (and who one way or another approved of it).

Maybe an Ack from a nvmx maintainer at least?

 -- Keir

> Jan

Xen-devel mailing list



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