From: Zhao Liu <zhao1.liu@linux.intel.com>
To: Qian Wen <qian.wen@intel.com>
Cc: qemu-devel@nongnu.org, xiaoyao.li@intel.com, zhao1.liu@intel.com
Subject: Re: [PATCH] target/i386: Avoid cpu number overflow in legacy topology
Date: Mon, 7 Aug 2023 16:08:04 +0800 [thread overview]
Message-ID: <ZNCmZJg0Sv1byFNM@liuzhao-OptiPlex-7080> (raw)
In-Reply-To: <20230728080150.2958048-1-qian.wen@intel.com>
On Fri, Jul 28, 2023 at 04:01:50PM +0800, Qian Wen wrote:
> Date: Fri, 28 Jul 2023 16:01:50 +0800
> From: Qian Wen <qian.wen@intel.com>
> Subject: [PATCH] target/i386: Avoid cpu number overflow in legacy topology
> X-Mailer: git-send-email 2.25.1
>
> The legacy topology enumerated by CPUID.1.EBX[23:16] is defined in SDM
> Vol2:
>
> Bits 23-16: Maximum number of addressable IDs for logical processors in
> this physical package.
>
> To avoid data overflow, limit the max value written to EBX[23:16] to
> 255.
>
> Signed-off-by: Qian Wen <qian.wen@intel.com>
> ---
> target/i386/cpu.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 1294be374ab2..70589a58b727 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -5356,6 +5356,7 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
> uint32_t die_offset;
> uint32_t limit;
> uint32_t signature[3];
> + uint32_t threads_per_socket;
> X86CPUTopoInfo topo_info;
>
> topo_info.dies_per_pkg = env->nr_dies;
> @@ -5397,8 +5398,18 @@ void cpu_x86_cpuid(CPUX86State *env, uint32_t index, uint32_t count,
> *ecx |= CPUID_EXT_OSXSAVE;
> }
> *edx = env->features[FEAT_1_EDX];
> - if (cs->nr_cores * cs->nr_threads > 1) {
> - *ebx |= (cs->nr_cores * cs->nr_threads) << 16;
> + /*
> + * The vCPU number more than 255 needs support of V2 Extended
> + * Topology enumerated by CPUID.0x1f or Extended Topology
> + * enumerated by CPUID.0x0b.
> + */
> + threads_per_socket = cs->nr_cores * cs->nr_threads;
> + if (threads_per_socket > 255) {
> + threads_per_socket = 255;
Straight encoding to 255 is good for me!
-Zhao
> + }
> +
> + if (threads_per_socket > 1) {
> + *ebx |= threads_per_socket << 16;
> *edx |= CPUID_HT;
> }
> /*
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-08-07 7:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 8:01 [PATCH] target/i386: Avoid cpu number overflow in legacy topology Qian Wen
2023-08-07 7:36 ` Xiaoyao Li
2023-08-07 10:08 ` Wen, Qian
2023-08-07 8:08 ` Zhao Liu [this message]
2023-08-07 10:10 ` Wen, Qian
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=ZNCmZJg0Sv1byFNM@liuzhao-OptiPlex-7080 \
--to=zhao1.liu@linux.intel.com \
--cc=qemu-devel@nongnu.org \
--cc=qian.wen@intel.com \
--cc=xiaoyao.li@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).