Re: [Xen-devel] [PATCH v2 03/10] x86/HVM: Call vlapic_destroy after vcpu_destroy

2017-01-10 Thread Suravee Suthikulpanit
On 01/05/2017 10:56 PM, Jan Beulich wrote: On 31.12.16 at 06:45, wrote: Since vlapic_init() is called before vcpu_initialise(). We should call the destroy functions in the the reverse order here. Double "the". And to quote from my RFC reply: "Also the ordering issue extends to other calls,

Re: [Xen-devel] [PATCH v2 03/10] x86/HVM: Call vlapic_destroy after vcpu_destroy

2017-01-05 Thread Jan Beulich
>>> On 31.12.16 at 06:45, wrote: > Since vlapic_init() is called before vcpu_initialise(). > We should call the destroy functions in the the reverse order here. Double "the". And to quote from my RFC reply: "Also the ordering issue extends to other calls, and I think if at all possible we shoul

Re: [Xen-devel] [PATCH v2 03/10] x86/HVM: Call vlapic_destroy after vcpu_destroy

2017-01-04 Thread Tian, Kevin
> From: Suravee Suthikulpanit [mailto:suravee.suthikulpa...@amd.com] > Sent: Saturday, December 31, 2016 1:46 PM > > Since vlapic_init() is called before vcpu_initialise(). > We should call the destroy functions in the the reverse order here. > > Signed-off-by: Suravee Suthikulpanit > Reviewed-b

[Xen-devel] [PATCH v2 03/10] x86/HVM: Call vlapic_destroy after vcpu_destroy

2016-12-30 Thread Suravee Suthikulpanit
Since vlapic_init() is called before vcpu_initialise(). We should call the destroy functions in the the reverse order here. Signed-off-by: Suravee Suthikulpanit Reviewed-by: Konrad Rzeszutek Wilk Cc: Boris Ostrovsky Cc: Jun Nakajima Cc: Kevin Tian --- xen/arch/x86/hvm/hvm.c | 4 ++-- 1 file