From: Willy Tarreau <willy@w.ods.org>
To: Ion Badulescu <ionut@badula.org>
Cc: Mikael Pettersson <mikpe@user.it.uu.se>,
m.c.p@wolk-project.de, Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org
Subject: Re: UP local APIC is deadly on SMP Athlon
Date: Sat, 22 Feb 2003 10:06:04 +0100 [thread overview]
Message-ID: <20030222090604.GC5411@alpha.home.local> (raw)
In-Reply-To: <Pine.LNX.4.44.0302220144530.18311-100000@moisil.badula.org>
Hi !
Good catch, Ion !
On Sat, Feb 22, 2003 at 03:05:37AM -0500, Ion Badulescu wrote:
> As a matter of fact, I got very interesting numbers from that printk() I
> added:
>
> - all the Intel and single proc AMD printed "0".
> - all the dual AMD machines printed "1".
Same here, dual AMD/760MPX.
BTW, there's something I don't understand. The only reference to
APIC_init_uniprocessor() I found was in smpboot.c:1044. It's called when the
SMP config has not been found at boot time (and it also sets
phys_cpu_present_map to 1, BTW). My problem is that this function is executed
on my dual-k7, on an SMP kernel (because I see the added message), but I
don't see the "SMP motherboard not detected" message which should be displayed
just before APIC_init_uniprocessor().
So I suspect there's something strange in this code that might explain why
only CPU0 receives the interrupts, but I don't understand the code path !
I'd appreciate it if someone has a clue... I can provide .config and dmesg
if needed. By this time, I'll add printk's everywhere in the kernel.
Cheers,
Willy
next prev parent reply other threads:[~2003-02-22 9:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 0:38 UP local APIC is deadly on SMP Athlon Mikael Pettersson
2003-02-22 8:05 ` Ion Badulescu
2003-02-22 9:06 ` Willy Tarreau [this message]
2003-02-22 9:19 ` Willy Tarreau
-- strict thread matches above, loose matches on Subject: below --
2003-02-20 15:05 Ion Badulescu
2003-02-21 0:12 ` Jeff Garzik
2003-02-21 2:03 ` Ion Badulescu
2003-02-21 14:47 ` Mikael Pettersson
2003-02-21 15:09 ` Ion Badulescu
2003-02-21 15:41 ` Mikael Pettersson
2003-02-21 20:42 ` Ion Badulescu
2003-02-21 21:41 ` Marc-Christian Petersen
2003-02-21 21:49 ` Ion Badulescu
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=20030222090604.GC5411@alpha.home.local \
--to=willy@w.ods.org \
--cc=ionut@badula.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.c.p@wolk-project.de \
--cc=mikpe@user.it.uu.se \
/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