From: Sean Christopherson <seanjc@google.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "Carlos López" <clopez@suse.de>,
"Jim Mattson" <jmattson@google.com>,
kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Thomas Gleixner" <tglx@kernel.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Dave Hansen" <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"open list:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<linux-kernel@vger.kernel.org>, "Babu Moger" <bmoger@amd.com>
Subject: Re: [PATCH] KVM: x86: synthesize TSA CPUID bits via SCATTERED_F()
Date: Wed, 11 Feb 2026 08:28:34 -0800 [thread overview]
Message-ID: <aYyuMkN56sNZBY9f@google.com> (raw)
In-Reply-To: <20260211161723.GDaYyrk9gZfONLoARz@fat_crate.local>
On Wed, Feb 11, 2026, Borislav Petkov wrote:
> On Wed, Feb 11, 2026 at 07:54:30AM -0800, Sean Christopherson wrote:
> > If the kernel tracks both raw CPUID *and* kernel caps, then KVM can use the
> > table without having to (re)do CPUID when configuring KVM's feature set. But
> > KVM would still need to have processing for SYNTHESIZED_F, PASSTHROUGH_F, and F,
> > to derive the correct state from the raw+kernel tables.
>
> That's what I meant - the macros and the confusion which one to use would go
> away.
Again, the macros would go away, but they would simply be replaced by labels in
a table. I.e. the "confusion" won't go away, because it can't simply disappear.
That knowledge must live somewhere.
next prev parent reply other threads:[~2026-02-11 16:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-08 16:42 [PATCH] KVM: x86: synthesize TSA CPUID bits via SCATTERED_F() Carlos López
2026-02-08 18:28 ` Borislav Petkov
2026-02-08 20:50 ` Jim Mattson
2026-02-08 21:13 ` Borislav Petkov
2026-02-09 5:48 ` Jim Mattson
2026-02-09 11:40 ` Carlos López
2026-02-09 15:06 ` Sean Christopherson
2026-02-09 15:32 ` Borislav Petkov
2026-02-09 16:29 ` Sean Christopherson
2026-02-09 17:45 ` Borislav Petkov
2026-02-09 21:12 ` Sean Christopherson
2026-02-10 20:07 ` Borislav Petkov
2026-02-10 23:48 ` Sean Christopherson
2026-02-11 13:32 ` Borislav Petkov
2026-02-11 15:54 ` Sean Christopherson
2026-02-11 16:17 ` Borislav Petkov
2026-02-11 16:28 ` Sean Christopherson [this message]
2026-02-09 10:02 ` Binbin Wu
2026-02-09 11:43 ` Carlos López
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=aYyuMkN56sNZBY9f@google.com \
--to=seanjc@google.com \
--cc=bmoger@amd.com \
--cc=bp@alien8.de \
--cc=clopez@suse.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@kernel.org \
--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.