From: Willy Tarreau <willy@w.ods.org>
To: Willy Tarreau <willy@w.ods.org>
Cc: Ion Badulescu <ionut@badula.org>,
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:19:05 +0100 [thread overview]
Message-ID: <20030222091905.GD5411@alpha.home.local> (raw)
In-Reply-To: <20030222090604.GC5411@alpha.home.local>
On Sat, Feb 22, 2003 at 10:06:04AM +0100, Willy Tarreau wrote:
> 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().
Oops ! Sorry for the noise, I confused the message about phys_id_present_map
with the one I added to APIC_init_uniprocessor(). So I confirm that this
function is NOT executed on my dual-k7.
Cheers,
Willy
next prev parent reply other threads:[~2003-02-22 9:23 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
2003-02-22 9:19 ` Willy Tarreau [this message]
-- 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=20030222091905.GD5411@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