linux-kernel - Re: [PATCH v2 1/1] KVM: VMX: configure SVI during runtime APICv activation

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] [day] [month] [year] [list]

Message-ID: <aTMkLVAwwocNvRae@google.com>
Date: Fri, 5 Dec 2025 10:27:57 -0800
From: Sean Christopherson <seanjc@...gle.com>
To: Dongli Zhang <dongli.zhang@...cle.com>
Cc: kvm@...r.kernel.org, x86@...nel.org, linux-kernel@...r.kernel.org, 
	chao.gao@...el.com, pbonzini@...hat.com, tglx@...utronix.de, mingo@...hat.com, 
	bp@...en8.de, dave.hansen@...ux.intel.com, hpa@...or.com, joe.jin@...cle.com, 
	alejandro.j.jimenez@...cle.com
Subject: Re: [PATCH v2 1/1] KVM: VMX: configure SVI during runtime APICv activation

On Fri, Dec 05, 2025, Dongli Zhang wrote:
> > But they're most definitely NOT stable material.  So my plan is to grab this
> > and the below for 6.19, and then do the cleanup for 6.20 or later.
> > 
> > Oh, almost forgot.  We can also sink the hwapic_isr_update() call into
> > kvm_apic_update_apicv() and drop kvm_apic_update_hwapic_isr() entirely, which is
> > another argument for your approach.  That's actually a really good fit, because
> > that's where KVM parses the vISR when APICv is being _disabled_.
> > 
> > I'll post a v3 with everything tomorrow (hopefully) after running the changes
> > through more normal test flow.
> 
> Looking forward for how it looks like. The only concern is if it is simple
> enough to backport to prior older kernel version, i.e. v5.15.196.

Oh, the fixes for stable/LTS are literally your patches.  The other stuff is going
on top; I've no intention of it being backported to 6.18, let alone 5.15 :-)