Re: [Xen-devel] [PATCH v2] sync CPU state upon final domain destruction

Hi, On 11/22/2017 01:00 PM, Jan Beulich wrote: On 22.11.17 at 13:39, wrote: See the code comment being added for why we need this. This is being placed here to balance between the desire to prevent future similar issues (the risk of which would grow if it was put further

Re: [Xen-devel] [PATCH v2] sync CPU state upon final domain destruction

>>> On 22.11.17 at 13:39, wrote: > See the code comment being added for why we need this. > > This is being placed here to balance between the desire to prevent > future similar issues (the risk of which would grow if it was put > further down the call stack, e.g. in

Re: [Xen-devel] [PATCH v2] sync CPU state upon final domain destruction

On 22/11/17 12:39, Jan Beulich wrote: > See the code comment being added for why we need this. > > This is being placed here to balance between the desire to prevent > future similar issues (the risk of which would grow if it was put > further down the call stack, e.g. in vmx_vcpu_destroy()) and

[Xen-devel] [PATCH v2] sync CPU state upon final domain destruction

See the code comment being added for why we need this. This is being placed here to balance between the desire to prevent future similar issues (the risk of which would grow if it was put further down the call stack, e.g. in vmx_vcpu_destroy()) and the intention to limit the performance impact