All of lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Kulke <magnuskulke@linux.microsoft.com>
To: Mohamed Mediouni <mohamed@unpredictable.fr>
Cc: qemu-devel@nongnu.org, Wei Liu <liuwe@microsoft.com>,
	Wei Liu <wei.liu@kernel.org>, Zhao Liu <zhao1.liu@intel.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Magnus Kulke <magnuskulke@microsoft.com>
Subject: Re: [PATCH 08/10] target/i386: query mshv accel for supported cpuids
Date: Fri, 13 Feb 2026 10:44:49 +0100	[thread overview]
Message-ID: <aY7ykd6xs1fo76M2@example.com> (raw)
In-Reply-To: <28261EA8-97DB-400F-A85C-4066A1AC425A@unpredictable.fr>

On Thu, Feb 12, 2026 at 12:35:57AM +0100, Mohamed Mediouni wrote:
> 
> Interesting. For WHPX on Arm, what’s done is creating a stub partition and extract CPUID info from
> it (with necessary guest stub code if necessary) but doing it this way like HVF x86 does is intriguing too…
> 
> Is this future-proof or are there catches with this approach?
> 

I think this is a valid approach that we also considered. I assume for
MSHV eventually we want to have a MSHV_GET_SUPPORTED_CPUID ioctl, similar
to what exists in KVM, so we can make centralize some decisions instead
of leaving it up to the VMM. This approach might end up using a dummy
partition inside the kernel, but would be an implementation detail.


  reply	other threads:[~2026-02-13  9:45 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11 15:54 [PATCH 00/10] Support QEMU cpu models in MSHV accelerator Magnus Kulke
2026-02-11 15:54 ` [PATCH 01/10] MAINTAINERS: fix magnuskulke email-address Magnus Kulke
2026-03-03 12:14   ` Peter Maydell
2026-03-03 12:53     ` Magnus Kulke
2026-02-11 15:54 ` [PATCH 02/10] include/hw/hyperv: add QEMU_PACKED to uapi structs Magnus Kulke
2026-02-11 15:54 ` [PATCH 03/10] accel/mshv: use mshv_create_partition_v2 payload Magnus Kulke
2026-02-11 23:43   ` Mohamed Mediouni
2026-02-13  9:54     ` Magnus Kulke
2026-02-12 13:32   ` Anirudh Rayabharam
2026-02-13 10:27     ` Magnus Kulke
2026-02-18  6:23     ` Wei Liu
2026-02-19 10:33       ` Anirudh Rayabharam
2026-02-19 20:16         ` Wei Liu
2026-02-11 15:54 ` [PATCH 04/10] target/i386/mshv: fix cpuid propagation bug Magnus Kulke
2026-02-18  6:24   ` Wei Liu
2026-02-11 15:54 ` [PATCH 05/10] target/i386/mshv: fix various cpuid traversal bugs Magnus Kulke
2026-02-11 15:54 ` [PATCH 06/10] target/i386/mshv: change cpuid mask to UINT32_MAX Magnus Kulke
2026-02-11 15:54 ` [PATCH 07/10] target/i386/mshv: set cpu model name on -cpu host Magnus Kulke
2026-02-11 15:54 ` [PATCH 08/10] target/i386: query mshv accel for supported cpuids Magnus Kulke
2026-02-11 23:35   ` Mohamed Mediouni
2026-02-13  9:44     ` Magnus Kulke [this message]
2026-02-20  9:50     ` Paolo Bonzini
2026-02-11 15:54 ` [PATCH 09/10] target/i386/mshv: populate xsave area offsets Magnus Kulke
2026-02-11 15:54 ` [PATCH 10/10] target/i386/mshv: filter out CET bits in cpuid Magnus Kulke
2026-03-02 18:34 ` [PATCH 00/10] Support QEMU cpu models in MSHV accelerator Paolo Bonzini
2026-03-03 13:30   ` Magnus Kulke
2026-03-03 14:04     ` Paolo Bonzini

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=aY7ykd6xs1fo76M2@example.com \
    --to=magnuskulke@linux.microsoft.com \
    --cc=liuwe@microsoft.com \
    --cc=magnuskulke@microsoft.com \
    --cc=mohamed@unpredictable.fr \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.liu@kernel.org \
    --cc=zhao1.liu@intel.com \
    /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.