[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH v2 3/3] x86/vmx: fix vmentry failure with TSX bits in LBR
On 22/02/17 13:58, Sergey Dyasli wrote: > >>> @@ -2876,7 +2938,11 @@ static int vmx_msr_write_intercept(unsigned int msr, >>> uint64_t msr_content) >>> for ( ; (rc == 0) && lbr->count; lbr++ ) >>> for ( i = 0; (rc == 0) && (i < lbr->count); i++ ) >>> if ( (rc = vmx_add_guest_msr(lbr->base + i)) == 0 ) >>> + { >>> vmx_disable_intercept_for_msr(v, lbr->base + i, >>> MSR_TYPE_R | MSR_TYPE_W); >>> + if ( vmx_lbr_tsx_fixup_needed ) >>> + v->arch.hvm_vmx.lbr_tsx_fixup_enabled = true; >> Is there anything wrong with >> >> v->arch.hvm_vmx.lbr_tsx_fixup_enabled = vmx_lbr_tsx_fixup_needed; >> >> ? > Only 80 characters limit prevented me from doing it that way. Splitting after the = is acceptable, e.g. v->arch.hvm_vmx.lbr_tsx_fixup_enabled = vmx_lbr_tsx_fixup_needed; ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |