From: Len Brown <len.brown@intel.com>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
mingo@elte.hu, linux-kernel <linux-kernel@vger.kernel.org>,
"Shah, Rajesh" <rajesh.shah@intel.com>,
John Stultz <johnstul@us.ibm.com>, Andi Kleen <ak@suse.de>,
Asit K Mallick <asit.k.mallick@intel.com>
Subject: RE: [RFC][PATCH] i386 x86-64 Eliminate Local APIC timer interrupt
Date: 05 May 2005 00:16:21 -0400 [thread overview]
Message-ID: <1115266581.7644.52.camel@d845pe> (raw)
In-Reply-To: <88056F38E9E48644A0F562A38C64FB60049EE972@scsmsx403.amr.corp.intel.com>
On Fri, 2005-04-29 at 22:43, Pallipadi, Venkatesh wrote:
> The patch as it is should handle 8259 case using the regular APIC
> timer. It only adds broadcast when IOAPIC is used for timer
> interrupt.
While they don't need the broadcast capability of this patch,
uniprocessors do need the change to stop using LAPIC timer
if they support C3 (as virtually all laptops do).
It was a mistake to allow using the LOC on a uniprocessor
in the first place -- as the UP system runs perfectly fine
with timers coming in on IRQ0 and doesn't need another interrupt.
Re: SMP using i8259
While Linux in ACPI mode allows "noapic" on SMP, it isn't recommended.
It is there for comparisons, debugging, and to work-around the odd
broken system. It is an exception configuration, and supporting it
should in no way impact the design for other 99.99% normal systems.
Indeed, note that SMP systems using i8259 instead of IOAPIC
is explicity forbidden by MPS, and thus would probably fail
the compatibility test for your favorite high volume binary OS.
-Len
next prev parent reply other threads:[~2005-05-05 4:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 2:43 [RFC][PATCH] i386 x86-64 Eliminate Local APIC timer interrupt Pallipadi, Venkatesh
2005-05-05 4:16 ` Len Brown [this message]
2005-05-05 12:03 ` Andi Kleen
2005-05-05 12:32 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2005-04-30 19:40 Protasevich, Natalie
2005-04-30 2:55 Pallipadi, Venkatesh
2005-04-30 3:06 ` Andrew Morton
2005-05-02 21:19 ` Pavel Machek
2005-04-30 0:26 Venkatesh Pallipadi
2005-04-30 0:46 ` Zwane Mwaikambo
2005-04-30 0:58 ` Zwane Mwaikambo
2005-04-30 1:13 ` Zwane Mwaikambo
2005-04-30 2:32 ` Andrew Morton
2005-05-02 16:38 ` Andi Kleen
2005-05-02 17:16 ` Venkatesh Pallipadi
2005-05-02 19:08 ` Andi Kleen
2005-05-02 20:27 ` Venkatesh Pallipadi
2005-05-03 14:17 ` Andi Kleen
2005-05-05 5:33 ` Len Brown
2005-05-05 12:19 ` Andi Kleen
2005-05-11 18:12 ` Tony Lindgren
2005-05-05 20:45 ` George Anzinger
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=1115266581.7644.52.camel@d845pe \
--to=len.brown@intel.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=asit.k.mallick@intel.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rajesh.shah@intel.com \
--cc=torvalds@osdl.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