linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: 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>,
	"Ahmed S. Darwish" <darwi@linutronix.de>,
	 linux-kernel@vger.kernel.org
Cc: Konstantin Belousov <kib@kib.kiev.ua>,
	John Baldwin <jhb@freebsd.org>,
	 "<cperciva@tarsnap.com>" <cperciva@tarsnap.com>
Subject: Re: [PATCH v3] x86/bhyve: Detect FreeBSD Bhyve hypervisor
Date: Fri, 15 Aug 2025 19:04:15 +0100	[thread overview]
Message-ID: <acf80fd2f7fa93b64e8f517d811330af0470ae33.camel@infradead.org> (raw)
In-Reply-To: <febd320e77386415b761d14fed7772b395b387bc.camel@infradead.org>

[-- Attachment #1: Type: text/plain, Size: 516 bytes --]

On Fri, 2025-08-15 at 14:03 +0100, David Woodhouse wrote:
> 
> +static uint32_t bhyve_features(void)
> +{
> +	if (bhyve_cpuid_max < bhyve_cpuid_base |
> CPUID_BHYVE_FEATURES)

Meh, needs parens around the 'bhyve_cpuid_base | CPUID_BHYVE_FEATURES',
which somehow I didn't see in the first build.

I shall persist in *trying* to get a Bhyve setup which actually manages
to boot a guest (or failing that, getting someone to boot it for me
since Bhyve clearly hates me) before sending v4 with that fixed.


[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]

      reply	other threads:[~2025-08-15 18:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15 13:03 [PATCH v3] x86/bhyve: Detect FreeBSD Bhyve hypervisor David Woodhouse
2025-08-15 18:04 ` David Woodhouse [this message]

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=acf80fd2f7fa93b64e8f517d811330af0470ae33.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=bp@alien8.de \
    --cc=cperciva@tarsnap.com \
    --cc=darwi@linutronix.de \
    --cc=dave.hansen@linux.intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).