[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.55.0804231855510.31934@cliff.in.clinika.pl>
Date: Wed, 23 Apr 2008 19:13:07 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
cc: Jean Delvare <jdelvare@...e.de>, Andi Kleen <andi@...stfloor.org>,
linux-pci@...ey.karlin.mff.cuni.cz,
LKML <linux-kernel@...r.kernel.org>, Pavel Machek <pavel@....cz>,
Tejun Heo <htejun@...il.com>,
Tom Long Nguyen <tom.l.nguyen@...el.com>,
Randy Dunlap <rdunlap@...otime.net>,
Jeff Garzik <jgarzik@...ox.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: PCI MSI breaks when booting with nosmp
On Wed, 23 Apr 2008, Jesse Barnes wrote:
> Yeah I think the patch is reasonable, would be good to get feedback from
> Thomas/Andi/Ingo though...
FWIW, the original idea behind "nosmp" or "maxcpus=0" (just as an
implementation detail) vs "maxcpus=1" was that the two formers would
disable the APIC circuitry altogether (including resisting from switching
from the PIC compatibility mode on systems supporting it), while the
latter would still boot UP, but with interrupts routed through the APICs.
Essentially SMP implied all the MP circuitry/provisions in this context,
the APICs being an inherent part of which. Therefore I think the original
idea of implying "pci=nomsi" with "nosmp" certainly looks more in the
spirit of the original setup to me.
However we have "nolapic" these days as well and with this new proposal
this option could effectively take over the old meaning of "nosmp" (you
cannot do SMP without the local APIC, so "nolapic nosmp" is redundant).
I am not entirely convinced it is the right way though...
Maciej
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists