On Wed, Dec 21, 2022 at 04:14:39PM +0800, Yu Zhang wrote: > > diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c > > index 9985dbb63e7b..16ddd3fcd3cb 100644 > > --- a/arch/x86/kvm/vmx/vmx.c > > +++ b/arch/x86/kvm/vmx/vmx.c > > @@ -2134,6 +2134,9 @@ static int vmx_set_msr(struct kvm_vcpu *vcpu, struct msr_data *msr_info) > > (!msr_info->host_initiated && > > !guest_cpuid_has(vcpu, X86_FEATURE_MPX))) > > return 1; > > + > > + data = kvm_untagged_addr(data, vcpu); > > Do we really need to take pains to trigger the kvm_untagged_addr() > unconditionally? I mean, LAM may not be enabled by the guest or even > not exposed to the guest at all. > Ouch... I just realized, that unlike the paging mode, LAM can be enabled per-thread, instead of per-VM... B.R. Yu
