It's possible domain has already been in log-dirty mode when creating vcpu, in which case we should enable PML for this vcpu if PML has been enabled for the domain.
Signed-off-by: Kai Huang <kai.hu...@linux.intel.com> --- xen/arch/x86/hvm/vmx/vmx.c | 23 +++++++++++++++++++++++ 1 file changed, 23 insertions(+) diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c index f11ac46..e5471b8 100644 --- a/xen/arch/x86/hvm/vmx/vmx.c +++ b/xen/arch/x86/hvm/vmx/vmx.c @@ -117,6 +117,29 @@ static int vmx_vcpu_initialise(struct vcpu *v) return rc; } + /* + * It's rare but still possible that domain has already been in log-dirty + * mode when vcpu is being created (commented by Tim), in which case we + * should enable PML for this vcpu if PML has been enabled for the domain, + * and failure to enable results in failure of creating this vcpu. + * + * Note even there's no vcpu created for the domain, vmx_domain_enable_pml + * will return successful in which case vmx_domain_pml_enabled will also + * return true. And even this is the first vcpu to be created with + * vmx_domain_pml_enabled being true, failure of enabling PML still results + * in failure of creating vcpu, to avoid complicated logic to revert PML + * style EPT table to non-PML style EPT table. + */ + if ( vmx_domain_pml_enabled(v->domain) ) + { + if ( (rc = vmx_vcpu_enable_pml(v)) != 0 ) + { + dprintk(XENLOG_ERR, "%pv: Failed to enable PML.\n", v); + vmx_destroy_vmcs(v); + return rc; + } + } + vpmu_initialise(v); vmx_install_vlapic_mapping(v); -- 2.1.0 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel