[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <3F71014C-5692-4180-BC6B-CCD7D2A827BB@zytor.com>
Date: Mon, 19 Jan 2026 22:30:01 -0800
From: Xin Li <xin@...or.com>
To: 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 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/
Powered by blists - more mailing lists