public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Dave Jones <davej@redhat.com>,
	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 13:50:18 +0100	[thread overview]
Message-ID: <20060306125018.GA1673@elf.ucw.cz> (raw)
In-Reply-To: <20060301043353.GJ28434@redhat.com>

On Út 28-02-06 23:33:53, Dave Jones wrote:
> On Wed, Mar 01, 2006 at 02:57:05PM +1100, Michael Ellerman wrote:
>  > On 1/20/06, Darrick J. Wong <djwong@us.ibm.com> wrote:
>  > > Hi there,
>  > >
>  > > Some old i386 systems have flaky APIC hardware that doesn't always work
>  > > right.  Right now, enabling the APIC code in Kconfig means that the APIC
>  > > code will try to activate the APICs unless 'noapic nolapic' are passed
>  > > to force them off.  The attached patch provides a config option to
>  > > change that default to keep the APICs off unless specified otherwise,
>  > > disables get_smp_config if we are not initializing the local APIC, and
>  > > makes init_apic_mappings not init the IOAPICs if they are disabled.
>  > > Note that the current behavior is maintained if
>  > > CONFIG_X86_UP_APIC_DEFAULT_OFF=n.
>  > Did this hit the floor?
> 
> It's still being kicked around.  I saw one patch off-list earlier this
> week that has some small improvements over the variant originally posted,
> but still had 1-2 kinks.
> 
>  > It strikes me as a pretty good solution. This
>  > is pretty nasty for newbies installing distro kernels, they get some
>  > of the way through an install and then their machine just locks - not
>  > good PR.
> 
> 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)?

> The big problem the patch solves is allowing it to be possible
> to build a kernel with UP APIC code, but disabled by default
> (Because there a lot of older machines that die horribly if it
>  was enabled by default).

Is adding "noapic nolapic" to default command line a big problem?
								Pavel
-- 
Web maintainer for suspend.sf.net (www.sf.net/projects/suspend) wanted...

  parent reply	other threads:[~2006-03-06 16:35 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 [this message]
2006-03-06 17:17       ` Dave Jones
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=20060306125018.GA1673@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=davej@redhat.com \
    --cc=djwong@us.ibm.com \
    --cc=lcm@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@ellerman.id.au \
    /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