From: David Woodhouse <dwmw2@infradead.org>
To: "Ahmed S. Darwish" <darwi@linutronix.de>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
Ingo Molnar <mingo@redhat.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Andrew Cooper <andrew.cooper3@citrix.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Sean Christopherson <seanjc@google.com>,
Peter Zijlstra <peterz@infradead.org>,
Christian Ludloff <ludloff@gmail.com>,
Sohil Mehta <sohil.mehta@intel.com>,
Maciej Wieczor-Retman <m.wieczorretman@pm.me>,
John Ogness <john.ogness@linutronix.de>,
x86@kernel.org, x86-cpuid@lists.linux.dev,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] x86-cpuid-db: Release v3.0
Date: Fri, 27 Mar 2026 09:17:11 +0000 [thread overview]
Message-ID: <646c19398708901454c7336e408d80f8695060fe.camel@infradead.org> (raw)
In-Reply-To: <acX0Drk_6qD97nbq@lx-t490>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Fri, 2026-03-27 at 04:05 +0100, Ahmed S. Darwish wrote:
> Hi,
>
> I'm happy to announce release 3.0 of the x86-cpuid-db project:
>
> https://gitlab.com/x86-cpuid.org/x86-cpuid-db
> https://gitlab.com/x86-cpuid.org/x86-cpuid-db/-/releases/v3.0
It still doesn't iterate over the hypervisor blocks at 0x4000_0x00 and
find all of them. Both Xen and KVM will advertise the Hyper-V leaves at
0x4000_0000 and then their own get shifted to 0x4000_0100. And now we
can host HyperV-enlightened Xen guests under KVM, perhaps we could do
HyperV, then Xen, then KVM at 0x4000_0200?
I was checking to see if it has all the ways to detect the Extended
Destination ID enlightenment documented in the last page ("Hypervisor
detection via CPUID") of https://david.woodhou.se/ExtDestId.pdf
I think I see the Xen and KVM bits there, and I guess reporting them
with different strings in feature.c is kind of OK? The Bhyve and
Viridian bits are missing.
Also, the leaf at 0x40000010 isn't necessarily VMware-specific; it's
seen elsewhere too. At least EC2 exposes it under KVM. See thread at
about https://lore.kernel.org/all/aLDo3F3KKW0MzlcH@google.com/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
next prev parent reply other threads:[~2026-03-27 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 3:05 Ahmed S. Darwish
2026-03-27 9:17 ` David Woodhouse [this message]
2026-03-30 20:22 ` Ahmed S. Darwish
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=646c19398708901454c7336e408d80f8695060fe.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ludloff@gmail.com \
--cc=m.wieczorretman@pm.me \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=seanjc@google.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=x86-cpuid@lists.linux.dev \
--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®