From: Hugh Dickins <hugh@veritas.com>
To: Andi Kleen <ak@suse.de>
Cc: 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 15:09:32 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.61.0501281506100.7207@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050128143010.GE6703@wotan.suse.de>
On Fri, 28 Jan 2005, Andi Kleen wrote:
> > I'm confused! Why do we need X86_APIC_OFF config option (but code
> > compiled in), with boot options "apic" or "lapic" to enable it,
> > when we already have the code compiled in, with boot options
> > "noapic" or "nolapic" to disable it?
>
> As you said. The distribution wants a kernel that has it disabled
> by default, but allows to enable it with an option without
> recompiling the kernel.
>
> None of the defaults allow this and my patch adds that with
> an option.
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?
I'm not going to be the only one confused by this!
Hugh
next prev parent reply other threads:[~2005-01-28 15:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 13:39 Andi Kleen
2005-01-28 14:27 ` Hugh Dickins
2005-01-28 14:30 ` Andi Kleen
2005-01-28 15:09 ` Hugh Dickins [this message]
2005-01-28 15:18 ` Andi Kleen
2005-01-28 15:46 ` Hugh Dickins
2005-01-28 15:49 ` Andi Kleen
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=Pine.LNX.4.61.0501281506100.7207@goblin.wat.veritas.com \
--to=hugh@veritas.com \
--cc=acpi-devel@lists.sourceforge.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®