mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ahmed S. Darwish" <darwi@linutronix.de>
To: David Woodhouse <dwmw2@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
	David Woodhouse <dwmw@amazon.co.uk>,
	linux-kernel@vger.kernel.org,
	Konstantin Belousov <kib@kib.kiev.ua>,
	John Baldwin <jhb@freebsd.org>,
	"<cperciva@tarsnap.com>" <cperciva@tarsnap.com>
Subject: Re: [PATCH v4] x86/bhyve: Detect FreeBSD Bhyve hypervisor
Date: Mon, 18 Aug 2025 11:41:38 +0200	[thread overview]
Message-ID: <aKL1Uj4R2Dj1pwB7@lx-t490> (raw)
In-Reply-To: <03802f6f7f5b5cf8c5e8adfe123c397ca8e21093.camel@infradead.org>

On Sat, 16 Aug 2025, David Woodhouse wrote:
>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
> Wheee, now actually tested under Bhyve.
>
> [    0.000000] Hypervisor detected: Bhyve
>
> v4:
>  • Add missing parens around (bhyve_cpuid_base | CPUID_BHYVE_FEATURES)
>  • Drop unneeded comment about x2apic support
>
> v3:
>  • Drop the cpuid_level check
>  • Define and use BHYVE_SIGNATURE
>  • Use the actual definition of CPUID_BHYVE_FEATURES and logical OR
>    instead of adding, as we do for other hypervisor leaves elsewhere
>  • Fix bhyve_cpuid_max miscalculation mistake
>

Thanks! For the CPUID bits:

Acked-by: Ahmed S. Darwish <darwi@linutronix.de>

  reply	other threads:[~2025-08-18  9:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 10:06 David Woodhouse
2025-08-18  9:41 ` Ahmed S. Darwish [this message]
2025-08-18 10:38 ` Borislav Petkov
2025-08-18 11:03   ` David Woodhouse
2025-08-18 13:58 ` [tip: x86/cpu] x86/cpu: " tip-bot2 for David Woodhouse

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=aKL1Uj4R2Dj1pwB7@lx-t490 \
    --to=darwi@linutronix.de \
    --cc=bp@alien8.de \
    --cc=cperciva@tarsnap.com \
    --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®