From: Andi Kleen <andi@firstfloor.org>
To: Jean Delvare <jdelvare@suse.de>
Cc: Andi Kleen <andi@firstfloor.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
linux-pci@atrey.karlin.mff.cuni.cz,
LKML <linux-kernel@vger.kernel.org>, Pavel Machek <pavel@ucw.cz>,
Tejun Heo <htejun@gmail.com>,
Tom Long Nguyen <tom.l.nguyen@intel.com>,
Randy Dunlap <rdunlap@xenotime.net>,
Jeff Garzik <jgarzik@pobox.com>
Subject: Re: PCI MSI breaks when booting with nosmp
Date: Mon, 21 Apr 2008 23:09:09 +0200 [thread overview]
Message-ID: <20080421210909.GC21028@one.firstfloor.org> (raw)
In-Reply-To: <200804212248.02986.jdelvare@suse.de>
> Both call disable_ioapic_setup(), so how can they not be the same?
See Jesse's explanation. Basically there is special code in the smp
boot up to handle 0 CPUs and it disables all APICs.
This is very old and crufty and somewhat obsolete logic,
but it is like that.
-Andi
next prev parent reply other threads:[~2008-04-21 21:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-17 19:40 PCI MSI breaks when booting with nosmp Jean Delvare
2008-04-17 20:08 ` Jesse Barnes
2008-04-17 20:25 ` Jean Delvare
2008-04-21 17:43 ` Jesse Barnes
2008-04-21 18:45 ` Andi Kleen
2008-04-21 19:06 ` Jesse Barnes
2008-04-21 19:35 ` Jesse Barnes
2008-04-21 19:41 ` Andi Kleen
2008-04-21 19:43 ` Pavel Machek
2008-04-21 19:44 ` Andi Kleen
2008-04-22 21:25 ` Pavel Machek
2008-04-22 23:07 ` Jesse Barnes
2008-04-21 20:20 ` Jean Delvare
2008-04-21 20:40 ` Jesse Barnes
2008-04-21 20:46 ` Andi Kleen
2008-04-21 20:48 ` Jean Delvare
2008-04-21 21:09 ` Andi Kleen [this message]
2008-04-21 21:14 ` Jesse Barnes
2008-04-22 13:27 ` Jean Delvare
2008-04-22 15:50 ` Jesse Barnes
2008-04-23 14:38 ` Jean Delvare
2008-04-23 15:12 ` Jesse Barnes
2008-04-23 18:13 ` Maciej W. Rozycki
2008-04-23 18:23 ` Jesse Barnes
2008-04-23 18:32 ` Jesse Barnes
2008-04-23 18:32 ` Jean Delvare
2008-04-23 18:38 ` Maciej W. Rozycki
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=20080421210909.GC21028@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=htejun@gmail.com \
--cc=jbarnes@virtuousgeek.org \
--cc=jdelvare@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--cc=tom.l.nguyen@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.