From: Andi Kleen <andi@firstfloor.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] I/O APIC: Timer through 8259A revamp
Date: Mon, 19 May 2008 16:50:27 +0200 [thread overview]
Message-ID: <483193B3.3090807@firstfloor.org> (raw)
In-Reply-To: <Pine.LNX.4.55.0805191459220.19879@cliff.in.clinika.pl>
> With the ACPI tables, hardware is modern enough the timer interrupt
> should be directly available, but is usually wired in the way recommended
> by the MP spec.
I originally had that assumption too, but in practice that doesn't seem
to be always the case unfortunately. Or sometimes the tests just fail
for whatever reason and they drop into the fallback path.
> That is the output of the master 8259A goes to INT0 of
> the I/O APIC (or is only connected to local APICs) and the timer is routed
> to INT2.
There are already a couple of wiring differences in common chipsets.
Mostly hurts on the fallback path especially when multiple sources are
enabled (then you might end up with duplicated interrupts, happened often
on ATI systems)
> The use of the local APIC timer as a replacement was recommended back
> then,
That was before CPU power saving was invented I guess @)
> but I think IRQ8 from the RTC was also a good solution,
Trouble on Linux is that RTC doesn't support any of the traditional HZ
values. I considered writing a RTC driver back then, but didn't do
it because of this.
On the other hand with wider use of tickless kernels and hrtimers it might
be tolerable to use non standard HZ,
-Andi
next prev parent reply other threads:[~2008-05-19 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-18 3:35 [PATCH] I/O APIC: Timer through 8259A revamp Maciej W. Rozycki
2008-05-19 12:30 ` Ingo Molnar
2008-05-19 13:57 ` Maciej W. Rozycki
2008-05-19 12:52 ` Andi Kleen
2008-05-19 14:25 ` Maciej W. Rozycki
2008-05-19 14:50 ` Andi Kleen [this message]
2008-05-19 22:08 ` Maciej W. Rozycki
2008-05-19 22:34 ` Andi Kleen
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=483193B3.3090807@firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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