From: Len Brown <lenb@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-acpi@vger.kernel.org, Bernard Pidoux <bernard.pidoux@upmc.fr>
Subject: Re: booting "nosmp" kernel causing ACPI errors
Date: Sat, 23 Oct 2010 01:55:31 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.00.1010230149431.29399@localhost.localdomain> (raw)
In-Reply-To: <20101021162503.8511f92a.akpm@linux-foundation.org>
is there a request to fix something here?
My preferred "fix" would be to delegte the "nosmp" boot option
and to make "maxcpus=0" be a synomym for "maxcpus=1".
nosmp was originally implemented to disable MPS,
which supplied both SMP, and IOAPIC support.
MPS is largely gone these days, replaced by ACPI
about 15 years ago.
It seems that when people use "nosmp" today, they expect
it to work like "maxcpus=1", but are surprised
that it effectively adds "noapic".
thanks,
Len Brown, Intel Open Source Technology Center
next prev parent reply other threads:[~2010-10-23 5:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4CB9D69D.60203@upmc.fr>
2010-10-21 23:25 ` booting "nosmp" kernel causing ACPI errors Andrew Morton
2010-10-23 5:55 ` Len Brown [this message]
[not found] ` <1287708483.2210.13.camel@rui>
2010-10-29 19:47 ` f6bvp
2010-10-29 19:47 ` Bernard Pidoux
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=alpine.LFD.2.00.1010230149431.29399@localhost.localdomain \
--to=lenb@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bernard.pidoux@upmc.fr \
--cc=linux-acpi@vger.kernel.org \
/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