From: Andi Kleen <ak@muc.de>
To: YhLu <YhLu@tyan.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way
Date: 2 Jun 2005 20:50:53 +0200
Date: Thu, 2 Jun 2005 20:50:53 +0200 [thread overview]
Message-ID: <20050602185053.GF1683@muc.de> (raw)
In-Reply-To: <3174569B9743D511922F00A0C94314230A403901@TYANWEB>
On Wed, Jun 01, 2005 at 08:16:35PM -0700, YhLu wrote:
> andi,
>
> in arch/x86_64/kernel/smboot.c, function detect_siblings(),
>
> because smp_num_siblings is always =1, so several lines can be removed.
What do you mean? On intel systems with HyperThreading it is > 1.
>
> for_each_online_cpu (cpu) {
> struct cpuinfo_x86 *c = cpu_data + cpu;
> *R* int siblings = 0;
> int i;
> *R* if (smp_num_siblings > 1) {
> *R* for_each_online_cpu (i) {
> *R* if (cpu_core_id[cpu] == cpu_core_id[i]) {
> *R* siblings++;
> *R* cpu_set(i, cpu_sibling_map[cpu]);
> *R* }
> *R* }
> *R* } else {
> *R* siblings++;
> cpu_set(cpu, cpu_sibling_map[cpu]);
> *R* }
>
>
> *R* if (siblings != smp_num_siblings) {
> *R* printk(KERN_WARNING
> *R* "WARNING: %d siblings found for CPU%d, should be %d\n",
> *R* siblings, cpu, smp_num_siblings);
> *R* smp_num_siblings = siblings;
> *R* }
>
> Also I found the workaround for hang on second node is
> adding one line in setup.c
> /* Low order bits define the core id (index of core in socket) */
> cpu_core_id[cpu] = phys_proc_id[cpu] & ((1 << bits)-1);
> /* Convert the APIC ID into the socket ID */
> phys_proc_id[cpu] >>= bits;
> + printk(KERN_INFO " CPU %d(%d) phys_proc_id %d Core %d\n",
> + cpu, c->x86_num_cores, phys_proc_id[cpu], cpu_core_id[cpu]);
That would just change the timing.
-Andi
next prev parent reply other threads:[~2005-06-02 18:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-02 3:16 2.6.12-rc5 is broken in nvidia Ck804 Opteron MB/with dual cor e dual way YhLu
2005-06-02 18:50 ` Andi Kleen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-02 3:26 YhLu
2005-06-02 18:51 ` Andi Kleen
2005-06-02 18:55 YhLu
2005-06-02 18:56 YhLu
2005-06-02 19:03 ` Dave Jones
2005-06-03 19:26 ` Siddha, Suresh B
2005-06-02 19:06 ` Ashok Raj
2005-06-02 20:42 YhLu
2005-06-03 16:09 ` Andi Kleen
2005-06-03 18:56 ` Siddha, Suresh B
2005-06-02 21:15 YhLu
2005-06-02 21:33 YhLu
2005-06-03 16:12 ` Andi Kleen
2005-06-02 21:34 YhLu
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=20050602185053.GF1683@muc.de \
--to=ak@muc.de \
--cc=YhLu@tyan.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox