From: Zhao Liu <zhao1.liu@intel.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Ewan Hai <ewanhai-oc@zhaoxin.com>,
pbonzini@redhat.com, xiaoyao.li@intel.com, ewanhai@zhaoxin.com,
cobechen@zhaoxin.com, qemu-devel@nongnu.org,
qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v4] target/i386: Fix model number of Zhaoxin YongFeng vCPU template
Date: Wed, 7 May 2025 21:04:18 +0800 [thread overview]
Message-ID: <aBtaUkEnm3bdeW4U@intel.com> (raw)
In-Reply-To: <cc878857-66e9-4599-9982-cf88fd1f320b@tls.msk.ru>
On Wed, May 07, 2025 at 02:30:50PM +0300, Michael Tokarev wrote:
> Date: Wed, 7 May 2025 14:30:50 +0300
> From: Michael Tokarev <mjt@tls.msk.ru>
> Subject: Re: [PATCH v4] target/i386: Fix model number of Zhaoxin YongFeng
> vCPU template
>
> On 25.04.2025 14:14, Ewan Hai wrote:
> > On 4/24/25 3:25 PM, Michael Tokarev wrote:
> > >
> > > On 15.04.2025 05:45, Ewan Hai wrote:
> > > > The model number was mistakenly set to 0x0b (11) in commit ff04bc1ac4.
> > > > The correct value is 0x5b. This mistake occurred because the extended
> > > > model bits in cpuid[eax=0x1].eax were overlooked, and only the base
> > > > model was used.
> > > >
> > > > Using the wrong model number can affect guest behavior. One known issue
> > > > is that vPMU (which relies on the model number) may fail to operate
> > > > correctly.
> > > >
> > > > This patch corrects the model field by introducing a new vCPU version.
> > > >
> > > > Additionally, it adds a "Preferred CPU models for Zhaoxin x86 hosts"
> > > > section in docs/system/cpu-models-x86.rst.inc to recommend the
> > > > appropriate Zhaoxin CPU model(s).
> > > >
> > > > Fixes: ff04bc1ac4 ("target/i386: Introduce Zhaoxin Yongfeng CPU model")
> > > > Signed-off-by: Ewan Hai <ewanhai-oc@zhaoxin.com>
> > > > Reviewed-by: Zhao Liu <zhao1.liu@intel.com>
> > >
> > > Is it a qemu-stable material (for 10.0.x)?
> > >
> > > I'm picking this one up, please let me know if I should not.
> >
> > I'm not sure if this should go into qemu-stable. Maybe Paolo Bonzini or
> > Zhao can answer?
>
> Ping? Paolo, Zhao, - can you comment please?
Sorry for late. Though I didn't find the similar case, without this
patch, the original model can't support vPMU function correctly.
Therefore I think it makes sense to include this patch into stable QEMU,
so that the Zhaoxin user could have a normal CPU model.
Thanks,
Zhao
next prev parent reply other threads:[~2025-05-07 12:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 2:45 [PATCH v4] target/i386: Fix model number of Zhaoxin YongFeng vCPU template Ewan Hai
2025-04-15 3:32 ` Zhao Liu
2025-04-24 7:25 ` Michael Tokarev
2025-04-25 11:14 ` Ewan Hai
2025-05-07 11:30 ` Michael Tokarev
2025-05-07 13:04 ` Zhao Liu [this message]
2025-05-07 13:43 ` Michael Tokarev
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=aBtaUkEnm3bdeW4U@intel.com \
--to=zhao1.liu@intel.com \
--cc=cobechen@zhaoxin.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=mjt@tls.msk.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=xiaoyao.li@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.