From: YhLu <YhLu@tyan.com>
To: Andi Kleen <ak@muc.de>
Cc: "'Mikael Pettersson'" <mikpe@csd.uu.se>,
jamesclv@us.ibm.com, Matt_Domsch@dell.com, discuss@x86-64.org,
linux-kernel@vger.kernel.org, suresh.b.siddha@intel.com
Subject: RE: 256 apic id for amd64
Date: Mon, 10 Jan 2005 11:41:02 -0800 [thread overview]
Message-ID: <3174569B9743D511922F00A0C94314230729139F@TYANWEB> (raw)
[-- Attachment #1: Type: text/plain, Size: 38 bytes --]
Please refer the patch.
Regards
YH
[-- Attachment #2: x86_64_phy_proc_id.patch --]
[-- Type: application/octet-stream, Size: 1134 bytes --]
664a665
> unsigned int n;
687c688,690
< if (c->cpuid_level >= 0x80000008) {
---
> n = cpuid_eax(0x80000000);
>
> if (n >= 0x80000008) {
698c701
< int cpu = c->x86_apicid;
---
> int cpu = c->x86_apicid; // that is initial apicid
725,749c728,730
< index_lsb = 0;
< index_msb = 31;
< /*
< * At this point we only support two siblings per
< * processor package.
< */
< if (smp_num_siblings > NR_CPUS) {
< printk(KERN_WARNING "CPU: Unsupported number of the siblings %d", smp_num_siblings);
< smp_num_siblings = 1;
< return;
< }
< tmp = smp_num_siblings;
< while ((tmp & 1) == 0) {
< tmp >>=1 ;
< index_lsb++;
< }
< tmp = smp_num_siblings;
< while ((tmp & 0x80000000 ) == 0) {
< tmp <<=1 ;
< index_msb--;
< }
< if (index_lsb != index_msb )
< index_msb++;
< phys_proc_id[cpu] = phys_pkg_id(index_msb);
<
---
>
> phys_proc_id[cpu] = c->x86_apicid >> hweight32(c->x86_num_cores - 1);
>
1067c1048
< seq_printf(m, "cpu cores\t: %d\n", c->x86_num_cores);
---
> seq_printf(m, "\ncpu cores\t: %d\n", c->x86_num_cores);
next reply other threads:[~2005-01-10 20:11 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 19:41 YhLu [this message]
2005-01-10 19:43 ` 256 apic id for amd64 Andi Kleen
2005-01-11 0:42 ` James Cleverdon
2005-01-11 3:28 ` Siddha, Suresh B
2005-01-11 4:42 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 19:11 YhLu
2005-01-11 19:04 YhLu
2005-01-10 20:48 YhLu
2005-01-10 20:46 YhLu
2005-01-11 5:36 ` Andi Kleen
2005-01-10 20:37 YhLu
2005-01-10 20:09 YhLu
2005-01-10 20:18 ` Andi Kleen
2005-01-10 18:48 YhLu
2005-01-10 18:45 ` Andi Kleen
2005-01-10 18:44 Andi Kleen
2005-01-11 4:04 ` Siddha, Suresh B
2005-01-11 4:39 ` Andi Kleen
2005-01-11 17:50 ` Andi Kleen
2005-01-08 2:53 YhLu
2005-01-09 23:56 ` James Cleverdon
2005-01-08 2:37 Mikael Pettersson
2005-01-08 15:46 ` Andi Kleen
2005-01-08 1:50 YhLu
2005-01-08 0:50 YhLu
2005-01-08 0:42 ` Andi Kleen
2005-01-08 0:28 YhLu
2005-01-08 0:26 ` James Cleverdon
2005-01-08 0:34 ` Andi Kleen
2005-01-08 0:04 YhLu
2005-01-08 0:12 ` James Cleverdon
2005-01-07 21:44 YhLu
2005-01-07 22:18 ` Andi Kleen
2005-01-07 21:14 YhLu
2005-01-07 21:12 ` Andi Kleen
2005-01-07 19:43 YhLu
2005-01-07 19:40 ` Andi Kleen
2005-01-07 18:27 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 18:19 YhLu
2005-01-07 19:29 ` Andi Kleen
2005-01-07 2:53 YhLu
2005-01-07 12:24 ` Andi Kleen
2005-01-08 1:30 ` James Cleverdon
2005-01-07 1:06 YhLu
2005-01-07 12:44 ` Andi Kleen
2004-12-30 23:19 YhLu
2004-12-30 23:16 YhLu
2004-12-29 4:43 YhLu
2004-12-30 18:45 ` Andi Kleen
2004-12-30 22:56 ` Matt Domsch
2004-12-30 23:26 ` Andi Kleen
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=3174569B9743D511922F00A0C94314230729139F@TYANWEB \
--to=yhlu@tyan.com \
--cc=Matt_Domsch@dell.com \
--cc=ak@muc.de \
--cc=discuss@x86-64.org \
--cc=jamesclv@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=suresh.b.siddha@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).