[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <32096607-8426-4743-9d56-3ebf27d278cf@intel.com>
Date: Tue, 20 Jan 2026 08:07:38 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Xin Li <xin@...or.com>, Chao Gao <chao.gao@...el.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, pbonzini@...hat.com, seanjc@...gle.com,
corbet@....net, tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, x86@...nel.org, hpa@...or.com, luto@...nel.org,
peterz@...radead.org, andrew.cooper3@...rix.com, hch@...radead.org,
sohil.mehta@...el.com
Subject: Re: [PATCH v9 19/22] KVM: nVMX: Handle FRED VMCS fields in nested VMX
context
On 1/19/26 22:30, Xin Li wrote:
>> On Dec 1, 2025, at 10:32 PM, Chao Gao <chao.gao@...el.com> wrote:
>>> + nested_vmx_set_intercept_for_msr(vmx, msr_bitmap_l1, msr_bitmap_l0,
>>> + MSR_IA32_FRED_RSP0, MSR_TYPE_RW);
>> Why is only this specific MSR handled? What about other FRED MSRs?
> Peter just gave a good explanation:
>
> https://lore.kernel.org/lkml/f0768546-a767-4d74-956e-b40128272a09@zytor.com/
Yup! It would be great to get some of that content into the changelogs
and comments.
Powered by blists - more mailing lists