[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aRZZoqxwTBa_16HU@google.com>
Date: Thu, 13 Nov 2025 14:20:18 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Xin Li <xin@...or.com>
Cc: linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
linux-doc@...r.kernel.org, pbonzini@...hat.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, chao.gao@...el.com,
hch@...radead.org, sohil.mehta@...el.com
Subject: Re: [PATCH v9 00/22] Enable FRED with KVM VMX
On Thu, Nov 06, 2025, Xin Li wrote:
>
> > On Oct 26, 2025, at 1:18 PM, Xin Li (Intel) <xin@...or.com> wrote:
> > Although FRED and CET supervisor shadow stacks are independent CPU
> > features, FRED unconditionally includes FRED shadow stack pointer
> > MSRs IA32_FRED_SSP[0123], and IA32_FRED_SSP0 is just an alias of the
> > CET MSR IA32_PL0_SSP. IOW, the state management of MSR IA32_PL0_SSP
> > becomes an overlap area, and Sean requested that FRED virtualization
> > to land after CET virtualization [1].
> >
> > With CET virtualization now merged in v6.18, the path is clear to submit
> > the FRED virtualization patch series :).
>
> Sean, what is the plan for the FRED patch series?
Review and merge it asap. Unfortunately, "asap" isn't all that soon, mostly
because I've been bogged down with non-upstream stuff. I'm hoping to dive in
next week (but take that with a grain of salt; I've more or less said that exact
thing to someone else for other patches for three weeks running).
Powered by blists - more mailing lists