From: Igor Mammedov <imammedo@redhat.com>
To: Qian Wen <qian.wen@intel.com>
Cc: qemu-devel@nongnu.org, xiaoyao.li@intel.com, zhao1.liu@intel.com,
pbonzini@redhat.com, richard.henderson@linaro.org,
babu.moger@amd.com
Subject: Re: [PATCH v2] target/i386: Avoid cpu number overflow in legacy topology
Date: Wed, 9 Aug 2023 13:14:26 +0200 [thread overview]
Message-ID: <20230809131426.1d9f5821@imammedo.users.ipa.redhat.com> (raw)
In-Reply-To: <20230809102732.3124908-1-qian.wen@intel.com>
On Wed, 9 Aug 2023 18:27:32 +0800
Qian Wen <qian.wen@intel.com> wrote:
> 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.
>
> When launching the VM with -smp 256, the value written to EBX[23:16] is
> 0 because of data overflow. If the guest only supports legacy topology,
> without V2 Extended Topology enumerated by CPUID.0x1f or Extended
> Topology enumerated by CPUID.0x0b to support over 255 CPUs, the return
> of the kernel invoking cpu_smt_allowed() is false and AP's bring-up will
> fail. Then only CPU 0 is online, and others are offline.
>
> To avoid this issue caused by overflow, limit the max value written to
> EBX[23:16] to 255.
what happens on real hw or in lack of thereof what SDM says about this
value when there is more than 255 threads?.
> Signed-off-by: Qian Wen <qian.wen@intel.com>
> ---
> Changes v1 -> v2:
> - Revise the commit message and comment to more clearer.
> - Rebased to v8.1.0-rc2.
> ---
> target/i386/cpu.c | 16 ++++++++++++++--
> 1 file changed, 14 insertions(+), 2 deletions(-)
>
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 97ad229d8b..6e1d88fbd7 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -6008,6 +6008,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;
> @@ -6049,8 +6050,19 @@ 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;
> + /*
> + * Only bits [23:16] represent the maximum number of addressable
> + * IDs for logical processors in this physical package.
> + * When thread_per_socket > 255, it will 1) overwrite bits[31:24]
> + * which is apic_id, 2) bits [23:16] get truncated.
> + */
> + threads_per_socket = cs->nr_cores * cs->nr_threads;
> + if (threads_per_socket > 255) {
> + threads_per_socket = 255;
> + }
> +
> + if (threads_per_socket > 1) {
> + *ebx |= threads_per_socket << 16;
> *edx |= CPUID_HT;
> }
> if (!cpu->enable_pmu) {
next prev parent reply other threads:[~2023-08-09 11:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 10:27 [PATCH v2] target/i386: Avoid cpu number overflow in legacy topology Qian Wen
2023-08-09 11:14 ` Igor Mammedov [this message]
2023-08-09 13:20 ` Wen, Qian
2023-08-09 13:47 ` Igor Mammedov
2023-08-13 10:49 ` Wen, Qian
2023-08-13 23:59 ` Zhao Liu
2023-08-14 6:32 ` 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=20230809131426.1d9f5821@imammedo.users.ipa.redhat.com \
--to=imammedo@redhat.com \
--cc=babu.moger@amd.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qian.wen@intel.com \
--cc=richard.henderson@linaro.org \
--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).