From: Sean Christopherson <seanjc@google.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: kvm@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, chao.gao@intel.com,
pbonzini@redhat.com, tglx@linutronix.de, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
joe.jin@oracle.com, alejandro.j.jimenez@oracle.com
Subject: Re: [PATCH v2 1/1] KVM: VMX: configure SVI during runtime APICv activation
Date: Fri, 5 Dec 2025 10:27:57 -0800 [thread overview]
Message-ID: <aTMkLVAwwocNvRae@google.com> (raw)
In-Reply-To: <2b0de566-0602-4a9e-9c5c-b947617f684f@oracle.com>
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 :-)
prev parent reply other threads:[~2025-12-05 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-10 6:32 [PATCH v2 1/1] KVM: VMX: configure SVI during runtime APICv activation Dongli Zhang
2025-11-10 7:08 ` Chao Gao
2025-11-12 14:47 ` Sean Christopherson
2025-11-13 3:06 ` Dongli Zhang
2025-11-13 21:13 ` Sean Christopherson
2025-11-18 3:36 ` Dongli Zhang
2025-12-05 2:15 ` Sean Christopherson
2025-12-05 18:12 ` Dongli Zhang
2025-12-05 18:27 ` Sean Christopherson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aTMkLVAwwocNvRae@google.com \
--to=seanjc@google.com \
--cc=alejandro.j.jimenez@oracle.com \
--cc=bp@alien8.de \
--cc=chao.gao@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dongli.zhang@oracle.com \
--cc=hpa@zytor.com \
--cc=joe.jin@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.