All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jade Cheng <chengjiayao@bytedance.com>
To: ehabkost@redhat.com, pbonzini@redhat.com
Cc: Jade Cheng <chengjiayao@bytedance.com>,
	qemu-devel@nongnu.org, pizhenwei@bytedance.com
Subject: [PATCH] Fix CPUID_Fn8000001E_EBX for AMD
Date: Wed, 30 Jun 2021 16:25:51 +0800	[thread overview]
Message-ID: <20210630082551.12956-1-chengjiayao@bytedance.com> (raw)

According to AMD64 Arch Programmer's Manual Appendix D,
bits 7:0 in Fn8000_001E_EBX should be physical core(s) per logical processor, not per die.

Signed-off-by: Jade Cheng <chengjiayao@bytedance.com>
---
 target/i386/cpu.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/target/i386/cpu.c b/target/i386/cpu.c
index a9fe1662d3..417f5ba81f 100644
--- a/target/i386/cpu.c
+++ b/target/i386/cpu.c
@@ -381,7 +381,13 @@ static void encode_topo_cpuid8000001e(X86CPU *cpu, X86CPUTopoInfo *topo_info,
      *  NOTE: CoreId is already part of apic_id. Just use it. We can
      *  use all the 8 bits to represent the core_id here.
      */
-    *ebx = ((topo_info->threads_per_core - 1) << 8) | (topo_ids.core_id & 0xFF);
+    uint32_t core_id = topo_ids.core_id;
+
+    if (IS_AMD_CPU(&cpu->env)) {
+        core_id = topo_ids.core_id + topo_ids.die_id * topo_info->cores_per_die;
+    }
+
+    *ebx = ((topo_info->threads_per_core - 1) << 8) | (core_id & 0xFF);
 
     /*
      * CPUID_Fn8000001E_ECX [Node Identifiers] (NodeId)
-- 
2.24.3 (Apple Git-128)



             reply	other threads:[~2021-06-30  8:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-30  8:25 Jade Cheng [this message]
2021-07-15  6:15 ` [PATCH] Fix CPUID_Fn8000001E_EBX for AMD 成家瑶
2021-07-26 21:00 ` Eduardo Habkost
2021-11-22 12:47   ` Jade Cheng

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=20210630082551.12956-1-chengjiayao@bytedance.com \
    --to=chengjiayao@bytedance.com \
    --cc=ehabkost@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=pizhenwei@bytedance.com \
    --cc=qemu-devel@nongnu.org \
    /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.