From: Eial Czerwacki <eial@scalemp.com>
To: linux-kernel@vger.kernel.org
Cc: "Shai Fultheim (Shai@ScaleMP.com)" <Shai@scalemp.com>
Subject: [PATCH] AMD: modify cpu probe from APICID to initial APICID
Date: Tue, 25 Oct 2011 13:49:33 +0200 [thread overview]
Message-ID: <4EA6A24D.1000400@scalemp.com> (raw)
In-Reply-To: <9B14D1490DDECA4E974F6B9FC9EBAB3140CD27436C@VMBX108.ihostexchange.net>
Make AMD probe processors using APICID rather than the initial APICID.
Signed-off-by: Eial Czerwacki<eial@scalemp.com>
Signed-off-by: Shai Fultheim<shai@scalemp.com>
---
--- a/arch/x86/kernel/cpu/amd.c 2011-09-14 05:58:19.542910736 -0700
+++ b/arch/x86/kernel/cpu/amd.c 2011-09-14 06:01:41.493209624 -0700
@@ -299,9 +299,9 @@ static void __cpuinit amd_detect_cmp(str
bits = c->x86_coreid_bits;
/* Low order bits define the core id (index of core in socket) */
- c->cpu_core_id = c->initial_apicid& ((1<< bits)-1);
+ c->cpu_core_id = c->apicid& ((1<< bits)-1);
/* Convert the initial APIC ID into the socket ID */
- c->phys_proc_id = c->initial_apicid>> bits;
+ c->phys_proc_id = c->apicid>> bits;
/* use socket ID also for last level cache */
per_cpu(cpu_llc_id, cpu) = c->phys_proc_id;
/* fixup topology information on multi-node processors */
next parent reply other threads:[~2011-10-25 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EA6695C.1000904@scalemp.com>
[not found] ` <9B14D1490DDECA4E974F6B9FC9EBAB3140CD274366@VMBX108.ihostexchange.net>
[not found] ` <4EA699B5.4030008@scalemp.com>
[not found] ` <9B14D1490DDECA4E974F6B9FC9EBAB3140CD27436C@VMBX108.ihostexchange.net>
2011-10-25 11:49 ` Eial Czerwacki [this message]
2011-10-25 21:51 ` [PATCH] AMD: modify cpu probe from APICID to initial APICID Yinghai Lu
2011-10-26 6:20 ` Eial Czerwacki
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=4EA6A24D.1000400@scalemp.com \
--to=eial@scalemp.com \
--cc=Shai@scalemp.com \
--cc=linux-kernel@vger.kernel.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.