From: Andi Kleen <ak@muc.de>
To: YhLu <YhLu@tyan.com>
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: 10 Jan 2005 21:18:59 +0100
Date: Mon, 10 Jan 2005 21:18:59 +0100 [thread overview]
Message-ID: <20050110201859.GB98279@muc.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C9431423072913A4@TYANWEB>
On Mon, Jan 10, 2005 at 12:09:48PM -0800, YhLu wrote:
> Try this one.
I don't think it will work at all on Intel HT systems, since
nobody initializes c->x86_num_cores there. phys_proc_id[]
is supposed to be the same on two HT siblings.
You'll either need to initialize c->x86_num_cores on Intel too.
But since Intel seems to have dual cores upcomming and you'll
want HyperThreading support too it would need to be a new field.
Alternatively you can split the function for AMD and Intel and
use the new algorithm on AMD only. Perhaps that's better.
In the later case I would only use it when CMP_LEGACY is set.
-Andi
next prev parent reply other threads:[~2005-01-10 20:20 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 20:09 256 apic id for amd64 YhLu
2005-01-10 20:18 ` Andi Kleen [this message]
-- 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 19:41 YhLu
2005-01-10 19:43 ` Andi Kleen
2005-01-11 0:42 ` James Cleverdon
2005-01-11 3:28 ` Siddha, Suresh B
2005-01-11 4:42 ` 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=20050110201859.GB98279@muc.de \
--to=ak@muc.de \
--cc=Matt_Domsch@dell.com \
--cc=YhLu@tyan.com \
--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 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.