> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Tuesday, January 10, 2017 10:42 PM
>
> >>> On 10.01.17 at 15:26, wrote:
> > On 10/01/17 14:15, Andrew Cooper wrote:
> >> On 10/01/17 14:03, Suravee Suthikulpanit wrote:
> >>> The order of destroy function calls in hvm_vcpu_destroy() should be
On 1/10/17 21:26, Andrew Cooper wrote:
On 10/01/17 14:15, Andrew Cooper wrote:
On 10/01/17 14:03, Suravee Suthikulpanit wrote:
The order of destroy function calls in hvm_vcpu_destroy() should be
the reverse of init calls in hvm_vcpu_initialise().
Signed-off-by: Suravee Suthikulpanit
Reviewe
>>> On 10.01.17 at 15:26, wrote:
> On 10/01/17 14:15, Andrew Cooper wrote:
>> On 10/01/17 14:03, Suravee Suthikulpanit wrote:
>>> The order of destroy function calls in hvm_vcpu_destroy() should be
>>> the reverse of init calls in hvm_vcpu_initialise().
>>>
>>> Signed-off-by: Suravee Suthikulpanit
On 10/01/17 14:15, Andrew Cooper wrote:
> On 10/01/17 14:03, Suravee Suthikulpanit wrote:
>> The order of destroy function calls in hvm_vcpu_destroy() should be
>> the reverse of init calls in hvm_vcpu_initialise().
>>
>> Signed-off-by: Suravee Suthikulpanit
>> Reviewed-by: Konrad Rzeszutek Wilk
On 10/01/17 14:03, Suravee Suthikulpanit wrote:
> The order of destroy function calls in hvm_vcpu_destroy() should be
> the reverse of init calls in hvm_vcpu_initialise().
>
> Signed-off-by: Suravee Suthikulpanit
> Reviewed-by: Konrad Rzeszutek Wilk
> Reviewed-by: Kevin Tian
> Cc: Jan Beulich
>
The order of destroy function calls in hvm_vcpu_destroy() should be
the reverse of init calls in hvm_vcpu_initialise().
Signed-off-by: Suravee Suthikulpanit
Reviewed-by: Konrad Rzeszutek Wilk
Reviewed-by: Kevin Tian
Cc: Jan Beulich
Cc: Boris Ostrovsky
---
Note: I separate this out from the pr
