From: David Woodhouse <dwmw2@infradead.org>
To: Sean Christopherson <seanjc@google.com>
Cc: Khushit Shah <khushit.shah@nutanix.com>,
pbonzini@redhat.com, kai.huang@intel.com, mingo@redhat.com,
x86@kernel.org, bp@alien8.de, hpa@zytor.com,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
dave.hansen@linux.intel.com, tglx@linutronix.de,
jon@nutanix.com, shaju.abraham@nutanix.com,
stable@vger.kernel.org
Subject: Re: [PATCH v4] KVM: x86: Add x2APIC "features" to control EOI broadcast suppression
Date: Fri, 12 Dec 2025 10:11:45 +0900 [thread overview]
Message-ID: <eb5d0c3ea959292fad2017451099ef9226cc2e6a.camel@infradead.org> (raw)
In-Reply-To: <aTtdXpV6Lq0wygZd@google.com>
[-- Attachment #1: Type: text/plain, Size: 806 bytes --]
On Thu, 2025-12-11 at 16:10 -0800, Sean Christopherson wrote:
> On Fri, Dec 12, 2025, David Woodhouse wrote:
> > On Thu, 2025-12-11 at 10:59 +0000, Khushit Shah wrote:
> > And my intent was that the in-kernel I/O APIC patch gets included as
> > *part* of this series, otherwise we're making a semantic change to the
> > ENABLE behaviour later.
>
> Hmm, my only concern on that front is that we'd be backporting effectively new
> functionality to stable@ kernels that isn't strictly necessary. But that's
> probably fine given that it requires userspace to opt-in.
Yeah. Arguably it's *all* a new capability and a 'new' (albeit 30 years
old!) feature.
I guess you could make an argument for *only* backporting the DISABLE
part to stable kernels and not the ENABLE part.... but don't :)
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2025-12-12 1:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-11 10:59 Khushit Shah
2025-12-11 18:59 ` Sean Christopherson
2025-12-12 5:44 ` Khushit Shah
2025-12-11 21:05 ` Huang, Kai
2025-12-12 0:01 ` David Woodhouse
2025-12-12 0:10 ` Sean Christopherson
2025-12-12 1:11 ` David Woodhouse [this message]
2025-12-12 7:08 ` Khushit Shah
2025-12-12 7:31 ` David Woodhouse
2025-12-12 8:16 ` Khushit Shah
2025-12-12 8:19 ` David Woodhouse
2025-12-12 8:27 ` Khushit Shah
2025-12-12 8:30 ` David Woodhouse
2025-12-17 12:06 ` Khushit Shah
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=eb5d0c3ea959292fad2017451099ef9226cc2e6a.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jon@nutanix.com \
--cc=kai.huang@intel.com \
--cc=khushit.shah@nutanix.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shaju.abraham@nutanix.com \
--cc=stable@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®