From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Jean Delvare <jdelvare@suse.de>, Andi Kleen <andi@firstfloor.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>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: PCI MSI breaks when booting with nosmp
Date: Wed, 23 Apr 2008 11:32:18 -0700 [thread overview]
Message-ID: <200804231132.19874.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <200804231123.46506.jbarnes@virtuousgeek.org>
On Wednesday, April 23, 2008 11:23 am Jesse Barnes wrote:
> On Wednesday, April 23, 2008 11:13 am Maciej W. Rozycki wrote:
> > 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...
>
> Yeah, I'm not particularly attached to either meaning. It looks like we'll
> setup the local apic on 32 bit if the NMI vector is a local apic one, so in
> that case at least the behavior will be the same.
>
> Anyway, we have two options:
> 1) make nosmp/maxcpus=1 imply nolapic (and therefore disable MSI too)
> 2) make nosmp enable the lapic (so MSI will work)
Err, nosmp/maxcpus=0...
next prev parent reply other threads:[~2008-04-23 18:33 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
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 [this message]
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=200804231132.19874.jbarnes@virtuousgeek.org \
--to=jbarnes@virtuousgeek.org \
--cc=andi@firstfloor.org \
--cc=htejun@gmail.com \
--cc=jdelvare@suse.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=macro@linux-mips.org \
--cc=pavel@ucw.cz \
--cc=rdunlap@xenotime.net \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox