From: David Woodhouse <dwmw2@infradead.org>
To: Khushit Shah <khushit.shah@nutanix.com>
Cc: "seanjc@google.com" <seanjc@google.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"kai.huang@intel.com" <kai.huang@intel.com>,
"mingo@redhat.com" <mingo@redhat.com>,
"x86@kernel.org" <x86@kernel.org>, "bp@alien8.de" <bp@alien8.de>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
Jon Kohler <jon@nutanix.com>,
Shaju Abraham <shaju.abraham@nutanix.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v4] KVM: x86: Add x2APIC "features" to control EOI broadcast suppression
Date: Fri, 12 Dec 2025 17:30:30 +0900 [thread overview]
Message-ID: <a6f65078f78f3a864056f4deae76dcfbaede9241.camel@infradead.org> (raw)
In-Reply-To: <AD54CBB2-98C1-45CD-B9D8-FDBF9892B84F@nutanix.com>
[-- Attachment #1: Type: text/plain, Size: 1141 bytes --]
On Fri, 2025-12-12 at 08:27 +0000, Khushit Shah wrote:
>
>
> > On 12 Dec 2025, at 1:49 PM, David Woodhouse <dwmw2@infradead.org> wrote:
> >
> > On Fri, 2025-12-12 at 08:16 +0000, Khushit Shah wrote:
> > > I thought the earlier discussion preferred
> > > kvm_lapic_ignore_suppress_eoi_broadcast(), but
> > > I’m not tied to it.
> >
> > I think some of that earlier discussion was 'informed' by me typing
> > code into my mailer, and managing to type an example whose name implied
> > the exact opposite of what the code actually returned. :)
> >
>
> Got it :), How about kvm_lapic_respect_suppress_eoi_broadcast()? It avoids the
> double-negative and keeps the semantics clear.
Sure. That gives us fairly clear separate helpers (in a .h file) which
control whether we *advertise* it, and whether we really *do* it.
With them giving consistent 'true' and 'false' for 'ENABLE' and
'DISABLE' modes respectively, and being *inconsistent* for the 'QUIRK'
mode.
You could even use the same switch() structure for both, with only the
default: case being different, to make it crystal clear what's going
on.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2025-12-12 8:30 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
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 [this message]
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=a6f65078f78f3a864056f4deae76dcfbaede9241.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®