QEMU-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Magnus Kulke <magnuskulke@linux.microsoft.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel <qemu-devel@nongnu.org>, Wei Liu <wei.liu@kernel.org>,
	Zhao Liu <zhao1.liu@intel.com>, Wei Liu <liuwe@microsoft.com>,
	Magnus Kulke <magnuskulke@microsoft.com>,
	qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v6 2/9] target/i386/mshv: fix cpuid propagation bug
Date: Mon, 29 Jun 2026 12:24:19 +0200	[thread overview]
Message-ID: <akJH0yXcf+BfMCe/@example.com> (raw)
In-Reply-To: <CABgObfaVgKfDbn_K_tqbemoK=q8XLam-GWGMFg9fCFNO9axHiA@mail.gmail.com>

On Sun, Jun 28, 2026 at 01:41:02PM +0200, Paolo Bonzini wrote:
> Il dom 28 giu 2026, 13:24 Michael Tokarev <mjt@tls.msk.ru> ha scritto:
> 
> > Hi!
> >
> > Is this a qemu-stable material (11.0.x)?
> > I'm not sure how matur mshww is to begin with, whenever it is worth to
> > consider for the stable series.
> >
> 
> I am not even sure anyone can run it outside Microsoft... That's probably a
> no ;)
> 
> Paolo
> 
> 
> > Thanks,
> >
> > /mjt
> >
> >

yup, I would concur. theoretically yes - it does fix a bug that exists
on the stable release, but the bug only surfaces for -cpu host model
selection, which will only be supported in a future release (with the
patch series of which this commit is a part of).

best,

magnus


  reply	other threads:[~2026-06-29 10:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-16 12:11 [PATCH v6 0/9] Support QEMU cpu models in MSHV accelerator Magnus Kulke
2026-04-16 12:11 ` [PATCH v6 1/9] accel/mshv: use mshv_create_partition_v2 payload Magnus Kulke
2026-04-30  8:43   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 2/9] target/i386/mshv: fix cpuid propagation bug Magnus Kulke
2026-04-30  9:05   ` Doru Blânzeanu
2026-06-28 11:24   ` Michael Tokarev
2026-06-28 11:41     ` Paolo Bonzini
2026-06-29 10:24       ` Magnus Kulke [this message]
2026-04-16 12:11 ` [PATCH v6 3/9] target/i386/mshv: fix various cpuid traversal bugs Magnus Kulke
2026-04-30  9:35   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 4/9] target/i386/mshv: change cpuid mask to UINT32_MAX Magnus Kulke
2026-04-30 11:27   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 5/9] target/i386/mshv: set cpu model name on -cpu host Magnus Kulke
2026-04-30 11:47   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 6/9] target/i386: query mshv accel for supported cpuids Magnus Kulke
2026-05-06 10:41   ` Doru Blânzeanu
2026-06-25 15:16   ` Paolo Bonzini
2026-06-26 13:37     ` Magnus Kulke
2026-04-16 12:11 ` [PATCH v6 7/9] target/i386/mshv: populate xsave area offsets Magnus Kulke
2026-05-06 11:02   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 8/9] target/i386/mshv: use hv-provided [0xD,1+2].EBX Magnus Kulke
2026-05-06 11:14   ` Doru Blânzeanu
2026-04-16 12:11 ` [PATCH v6 9/9] accel/mshv: disable la57 (5lvl paging) Magnus Kulke
2026-05-06 11:24   ` Doru Blânzeanu

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=akJH0yXcf+BfMCe/@example.com \
    --to=magnuskulke@linux.microsoft.com \
    --cc=liuwe@microsoft.com \
    --cc=magnuskulke@microsoft.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox