From: Len Brown <len.brown@intel.com>
To: Natalie Protasevich <Natalie.Protasevich@UNISYS.com>
Cc: Andrew Morton <akpm@osdl.org>, Andi Kleen <ak@suse.de>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [patch 1/1] Do not enforce unique IO_APIC_ID for Xeon processors in EM64T mode (x86_64)
Date: 06 May 2005 13:34:08 -0400 [thread overview]
Message-ID: <1115400848.12770.10.camel@d845pe> (raw)
In-Reply-To: <20050505221117.508BB42AE4@linux.site>
On Thu, 2005-05-05 at 18:11, Natalie.Protasevich@unisys.com wrote:
>
> This patch disables unique IO_APIC_ID check for xAPIC systems running
> in EM64T mode. Xeon-based ES7000s panic failing this unnecessary
> check. I added IOAPIC_ID_CHECK config option and turned it off for
> Intel processors. Also added the boot option that overrides default
> and turnes this check on/off in case it is needed for some reason.
> Hope this is acceptable way to fix the problem.
>
> Signed-off by: Natalie Protasevich <Natalie.Protasevich@unisys.com>
>
> +config NO_IOAPIC_CHECK
> + bool
> + depends on GENERIC_CPU || MPSC
> + default y
> +
A run-time solution would be preferable to adding
a config option that only changes the default behaviour.
In general, the more config options, the more kernels
we force distros to build and support. We really want
to going the other way and simplifying, when possible.
cheers,
-Len
next prev parent reply other threads:[~2005-05-06 17:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-05 22:11 Natalie.Protasevich
2005-05-06 17:34 ` Len Brown [this message]
2005-05-06 17:57 ` Zwane Mwaikambo
2005-05-07 13:41 ` Andi Kleen
2005-05-07 5:34 Natalie.Protasevich
2005-05-08 1:00 ` Zwane Mwaikambo
2005-05-08 5:01 Protasevich, Natalie
2005-05-08 13:49 ` Andi Kleen
2005-05-09 19:15 ` James Cleverdon
2005-05-08 17:28 Protasevich, Natalie
2005-05-08 23:53 ` Andi Kleen
2005-05-11 7:10 Protasevich, Natalie
2005-05-11 11:22 ` Andi Kleen
2005-05-11 16:21 Protasevich, Natalie
2005-05-11 19:22 ` Andi Kleen
2005-05-12 2:22 Protasevich, Natalie
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=1115400848.12770.10.camel@d845pe \
--to=len.brown@intel.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=venkatesh.pallipadi@intel.com \
--cc=zwane@arm.linux.org.uk \
/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®