From: Borislav Petkov <bp@alien8.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
David Woodhouse <dwmw@amazon.co.uk>,
"Ahmed S. Darwish" <darwi@linutronix.de>,
linux-kernel@vger.kernel.org,
Konstantin Belousov <kib@kib.kiev.ua>,
John Baldwin <jhb@freebsd.org>
Subject: Re: [RFC PATCH] x86/bhyve: Detect FreeBSD Bhyve hypervisor
Date: Thu, 14 Aug 2025 12:15:52 +0200 [thread overview]
Message-ID: <20250814101552.GAaJ23WBZ-O3Yuu64t@fat_crate.local> (raw)
In-Reply-To: <98dd43553b2d63edd3d994816f378985d1a19d72.camel@infradead.org>
On Mon, Aug 11, 2025 at 01:16:42PM +0200, David Woodhouse wrote:
> From: David Woodhouse <dwmw@amazon.co.uk>
>
> This detects the Bhyve hypervisor
Users of this are?
Wikipedia says it already supports Linux :-P
> and enables 15-bit MSI support if
> available.
>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
> RFC because the CPUID_BHYVE_FEATURES leaf is submitted to FreeBSD in
Which makes it, what, 0x4000_0001?
I presume there's an agreement among all the hypervisors...?
> https://github.com/freebsd/freebsd-src/pull/1797 and not yet merged.
> And because I haven't tested this patch at all other than building it.
>
> It's tiny so I didn't put it behind a separate CONFIG_BHYVE_GUEST.
> Should I?
Yeah, please do.
> +/* Features advertised in CPUID_BHYVE_FEATURES %eax */
> +#define CPUID_BHYVE_FEAT_EXT_DEST_ID (1UL << 0) /* MSI Extended Dest ID */
> +
> +static uint32_t __init bhyve_detect(void)
> +{
> + if (boot_cpu_data.cpuid_level < 0 ||
> + !boot_cpu_has(X86_FEATURE_HYPERVISOR))
cpu_feature_enabled()
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2025-08-14 10:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 11:16 David Woodhouse
2025-08-13 21:07 ` David Woodhouse
2025-08-14 10:15 ` Borislav Petkov [this message]
2025-08-14 11:13 ` David Woodhouse
2025-08-14 16:51 ` 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=20250814101552.GAaJ23WBZ-O3Yuu64t@fat_crate.local \
--to=bp@alien8.de \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=dwmw2@infradead.org \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=jhb@freebsd.org \
--cc=kib@kib.kiev.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 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®