linux-kernel - Re: [PATCH v4 00/19] Enable FRED with KVM VMX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <80ba45cf-2679-471b-ae3d-986697089b75@zytor.com>
Date: Tue, 24 Jun 2025 10:43:26 -0700
From: Xin Li <xin@...or.com>
To: Sean Christopherson <seanjc@...gle.com>
Cc: pbonzini@...hat.com, kvm@...r.kernel.org, linux-doc@...r.kernel.org,
        linux-kernel@...r.kernel.org, corbet@....net, tglx@...utronix.de,
        mingo@...hat.com, bp@...en8.de, dave.hansen@...ux.intel.com,
        x86@...nel.org, hpa@...or.com, andrew.cooper3@...rix.com,
        luto@...nel.org, peterz@...radead.org, chao.gao@...el.com,
        xin3.li@...el.com
Subject: Re: [PATCH v4 00/19] Enable FRED with KVM VMX

On 6/24/2025 10:06 AM, Sean Christopherson wrote:
> On Fri, Mar 28, 2025, Xin Li wrote:
>> Any chance we could merge FRED ahead of CET?
> 
> Probably not?  CET exists is publicly available CPUs.  AFAIK, FRED does not.

Better not, as you said it creates extra effort because FRED does lean a
bit on CET.

I was a bit worried that CET would take longer time than expected...

> And CET is (/knock wood) hopefully pretty much ready?  FWIW, I'd really like to

That is also my reading on CET.

> get both CET and FRED virtualization landed by 6.18, i.e. in time for the next
> LTS.

I love the plan!

FRED is my top priority.  I’ll address all your comments, rebase onto
kvm-x86/next (you have not updated yet :) ), and send out v5 at an
appropriate time.

Thanks!
      Xin