From: Zhao Liu <zhao1.liu@intel.com>
To: Ewan Hai <ewanhai-oc@zhaoxin.com>
Cc: pbonzini@redhat.com, qemu-devel@nongnu.org, ewanhai@zhaoxin.com,
cobechen@zhaoxin.com, Xudong Hao <xudong.hao@intel.com>
Subject: Re: [PATCH v2 1/4] target/i386: Add an option in X86CPUDefinition to control CPUID 0x1f
Date: Tue, 25 Nov 2025 15:37:16 +0800 [thread overview]
Message-ID: <aSVcrBGfR6WlnsMB@intel.com> (raw)
In-Reply-To: <20251027102139.270662-2-ewanhai-oc@zhaoxin.com>
On Mon, Oct 27, 2025 at 06:21:36AM -0400, Ewan Hai wrote:
> Date: Mon, 27 Oct 2025 06:21:36 -0400
> From: Ewan Hai <ewanhai-oc@zhaoxin.com>
> Subject: [PATCH v2 1/4] target/i386: Add an option in X86CPUDefinition to
> control CPUID 0x1f
> X-Mailer: git-send-email 2.34.1
>
> From: Zhao Liu <zhao1.liu@intel.com>
>
> Many Intel and Zhaoxin CPUs enable CPUID 0x1f by default to encode CPU
> topology information.
>
> Add the "cpuid_0x1f" option to X86CPUDefinition to allow named CPU
> models to configure CPUID 0x1f from the start, thereby forcing 0x1f
> to be present for guest.
>
> With this option, there's no need to explicitly add v1 model to an
> unversioned CPU model for explicitly enabling the x-force-cpuid-0x1f
> property.
>
> Tested-by: Xudong Hao <xudong.hao@intel.com>
> Signed-off-by: Zhao Liu <zhao1.liu@intel.com>
> ---
> target/i386/cpu.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
Thanks! I also mentioned this in my series:
https://lore.kernel.org/qemu-devel/20251120071030.961230-8-zhao1.liu@intel.com/
Regards,
Zhao
next prev parent reply other threads:[~2025-11-25 7:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 10:21 [PATCH v2 0/4] target/i386: Add support for Zhaoxin Shijidadao vCPU models Ewan Hai
2025-10-27 10:21 ` [PATCH v2 1/4] target/i386: Add an option in X86CPUDefinition to control CPUID 0x1f Ewan Hai
2025-11-25 7:37 ` Zhao Liu [this message]
2025-10-27 10:21 ` [PATCH v2 2/4] target/i386: Add cache model for Zhaoxin Shijidadao vCPUs Ewan Hai
2025-11-25 7:15 ` Zhao Liu
2025-10-27 10:21 ` [PATCH v2 3/4] target/i386: Introduce Zhaoxin Shijidadao-Client CPU model Ewan Hai
2025-11-25 7:35 ` Zhao Liu
2025-11-25 8:57 ` Ewan Hai
2025-12-15 9:03 ` Zhao Liu
2026-01-05 10:11 ` Ewan Hai
2026-01-07 3:55 ` Zhao Liu
2026-01-07 3:36 ` Ewan Hai
2025-10-27 10:21 ` [PATCH v2 4/4] target/i386: Introduce Zhaoxin Shijidadao-Server " Ewan Hai
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=aSVcrBGfR6WlnsMB@intel.com \
--to=zhao1.liu@intel.com \
--cc=cobechen@zhaoxin.com \
--cc=ewanhai-oc@zhaoxin.com \
--cc=ewanhai@zhaoxin.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=xudong.hao@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.