[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [PATCH 1/3] [RFC] x86/hvm: Permit HVM_PARAM_IDENT_PT to be set more than once
There is no conceptual problem with setting this parameter more than once. Checkpointed migration streams will typically set it once per checkpoint to the same value. The parameter is only actually needed on early-generation VT-x which lacked the unrestricted guest capability, although it could plausibly be used on newer VT-x with unusual execution control settings. Short circuit the expensive operations on non VT-x hardware. The parameter itself must always be latched to avoid issues if the VM eventually migrates to a host which needs to use the pagetable. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> CC: Keir Fraser <keir@xxxxxxx> CC: Jan Beulich <JBeulich@xxxxxxxx> CC: Yang Hongyang <yanghy@xxxxxxxxxxxxxx> --- xen/arch/x86/hvm/hvm.c | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c index 8140a27..5824e43 100644 --- a/xen/arch/x86/hvm/hvm.c +++ b/xen/arch/x86/hvm/hvm.c @@ -5730,12 +5730,13 @@ static int hvmop_set_param( rc = -EINVAL; break; case HVM_PARAM_IDENT_PT: - rc = -EINVAL; - if ( d->arch.hvm_domain.params[a.index] != 0 ) - break; - rc = 0; - if ( !paging_mode_hap(d) ) + d->arch.hvm_domain.params[a.index] = a.value; + /* + * Only actually required for VT-x lacking unrestricted_guest + * capabilities. Short circuit the pause if possible. + */ + if ( !paging_mode_hap(d) || !cpu_has_vmx ) break; /* @@ -5749,7 +5750,6 @@ static int hvmop_set_param( rc = 0; domain_pause(d); - d->arch.hvm_domain.params[a.index] = a.value; for_each_vcpu ( d, v ) paging_update_cr3(v); domain_unpause(d); -- 1.7.10.4 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |