From: Dave Jones <davej@redhat.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Michael Ellerman <michael@ellerman.id.au>,
"Darrick J. Wong" <djwong@us.ibm.com>,
linux-kernel@vger.kernel.org, Chris McDermott <lcm@us.ibm.com>
Subject: Re: [PATCH] leave APIC code inactive by default on i386
Date: Mon, 6 Mar 2006 12:17:47 -0500 [thread overview]
Message-ID: <20060306171747.GN21445@redhat.com> (raw)
In-Reply-To: <20060306125018.GA1673@elf.ucw.cz>
On Mon, Mar 06, 2006 at 01:50:18PM +0100, Pavel Machek wrote:
> > The number of systems that actually *need* APIC enabled are in the
> > vast (though growing) minority, so it's unlikely that most newbies
> > will hit this. The problem is also the inverse of what you describe.
> > Typically the distros have DMI lists of machines that *need* APIC
> > to make it enabled by default so everything 'just works'.
>
> Well, blacklisting "new" machines is a problem -- their number
> grows. Would not it be better to blacklist machines broken by APIC
> ("old" ones, presumably)?
It would. Though some new machines also falsely advertise it as
working aparently. I heard a report of a thinkpad going boom last week.
> Is adding "noapic nolapic" to default command line a big problem?
For end-users, yes. People want things to 'just work', not have
to find arcane commands to type in to make things work.
Dave
--
http://www.codemonkey.org.uk
next prev parent reply other threads:[~2006-03-06 17:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-20 1:20 [PATCH] leave APIC code inactive by default on i386 Darrick J. Wong
2006-01-20 14:42 ` Jan Engelhardt
2006-03-01 3:57 ` Michael Ellerman
2006-03-01 4:33 ` Dave Jones
2006-03-01 5:10 ` Michael Ellerman
2006-03-01 13:38 ` Dave Jones
2006-03-01 13:52 ` Matthew Garrett
2006-03-01 6:36 ` Zwane Mwaikambo
2006-03-01 13:39 ` Dave Jones
2006-03-01 21:29 ` Darrick J. Wong
2006-03-01 22:14 ` Dave Jones
2006-03-01 22:47 ` Darrick J. Wong
2006-03-01 22:51 ` Dave Jones
2006-03-01 23:29 ` Darrick J. Wong
2006-03-06 12:50 ` Pavel Machek
2006-03-06 17:17 ` Dave Jones [this message]
2006-03-06 17:41 ` Pavel Machek
2006-03-06 17:52 ` Dave Jones
2006-03-06 17:58 ` Pavel Machek
2006-03-06 18:17 ` Dave Jones
2006-03-06 19:05 ` Darrick J. Wong
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=20060306171747.GN21445@redhat.com \
--to=davej@redhat.com \
--cc=djwong@us.ibm.com \
--cc=lcm@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@ellerman.id.au \
--cc=pavel@ucw.cz \
/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.