linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andi Kleen <ak@suse.de>,
	akpm@osdl.org, linux-kernel@vger.kernel.org,
	acpi-devel@lists.sourceforge.net
Subject: Re: [PATCH] Add CONFIG_X86_APIC_OFF for i386/UP
Date: Fri, 28 Jan 2005 16:49:53 +0100	[thread overview]
Message-ID: <20050128154953.GJ6703@wotan.suse.de> (raw)
In-Reply-To: <Pine.LNX.4.61.0501281534420.7304@goblin.wat.veritas.com>

On Fri, Jan 28, 2005 at 03:46:05PM +0000, Hugh Dickins wrote:
> On Fri, 28 Jan 2005, Andi Kleen wrote:
> 
> > > Forgive me for not wading through the code, but it really needs to
> > > be spelt out in the comments: what's wrong with the existing kernel,
> > > with "noapic nolapic" in the distro's bootstring by default?
> > 
> > It's harder to explain and traditionally in LILO you couldn't remove
> > any options (in grub you can now).
> 
> And it's just that initial installation boot, via grub, which really
> matters.  Thereafter can be edited, before perhaps switching to LILO.

I now remember another reason for it: upgrades. SUSE always did it this
way (It goes back many moons to 2.2 based kernels when the UP APIC code
was added). It would be probably rather fragile to change this
automatically during an update.

I realize this isn't a big concern for mainline, but given that
people are always complaining about distributions having too many
patches it may be still good to add it to mainline because 
the SUSE kernel has it. Unless people think it is totally unsuitable (?),
but I don't think it is that bad.

Also I must add in addition to the CONFIG there are valuable bugfixes
in there too.

-Andi


  reply	other threads:[~2005-01-28 15:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-28 13:39 [PATCH] Add CONFIG_X86_APIC_OFF for i386/UP Andi Kleen
2005-01-28 14:27 ` Hugh Dickins
2005-01-28 14:30   ` Andi Kleen
2005-01-28 15:09     ` Hugh Dickins
2005-01-28 15:18       ` Andi Kleen
2005-01-28 15:46         ` Hugh Dickins
2005-01-28 15:49           ` Andi Kleen [this message]
2005-01-28 17:28             ` Adrian Bunk
2005-01-28 17:43         ` Zwane Mwaikambo
2005-01-28 17:46           ` Andi Kleen
2005-01-28 18:30             ` Hugh Dickins

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=20050128154953.GJ6703@wotan.suse.de \
    --to=ak@suse.de \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).