Re: [Xen-devel] [PATCH] x86: restrict HVMOP_pagetable_dying to current

2018-10-15 Thread George Dunlap
On 10/05/2018 12:29 PM, Jan Beulich wrote: > This is not used (and probably was never meant to be) by the tool stack. > Limiting it to the current domain in particular allows to eliminate a > bogus use of vCPU 0 in pagetable_dying(). > > Remove the now unnecessary domain/vCPU parameters from the w

Re: [Xen-devel] [PATCH] x86: restrict HVMOP_pagetable_dying to current

2018-10-12 Thread Wei Liu
On Fri, Oct 05, 2018 at 05:29:30AM -0600, Jan Beulich wrote: > This is not used (and probably was never meant to be) by the tool stack. > Limiting it to the current domain in particular allows to eliminate a > bogus use of vCPU 0 in pagetable_dying(). > > Remove the now unnecessary domain/vCPU par

Re: [Xen-devel] [PATCH] x86: restrict HVMOP_pagetable_dying to current

2018-10-05 Thread Jan Beulich
>>> On 05.10.18 at 13:58, wrote: > On 05/10/18 12:29, Jan Beulich wrote: >> This is not used (and probably was never meant to be) by the tool stack. >> Limiting it to the current domain in particular allows to eliminate a >> bogus use of vCPU 0 in pagetable_dying(). >> >> Remove the now unnecessar

Re: [Xen-devel] [PATCH] x86: restrict HVMOP_pagetable_dying to current

2018-10-05 Thread Andrew Cooper
On 05/10/18 12:29, Jan Beulich wrote: > This is not used (and probably was never meant to be) by the tool stack. > Limiting it to the current domain in particular allows to eliminate a > bogus use of vCPU 0 in pagetable_dying(). > > Remove the now unnecessary domain/vCPU parameters from the wrapper

[Xen-devel] [PATCH] x86: restrict HVMOP_pagetable_dying to current

2018-10-05 Thread Jan Beulich
This is not used (and probably was never meant to be) by the tool stack. Limiting it to the current domain in particular allows to eliminate a bogus use of vCPU 0 in pagetable_dying(). Remove the now unnecessary domain/vCPU parameters from the wrapper/hook functions at the same time. Signed-off-b