From: Andi Kleen <andi@firstfloor.org>
To: yuhong <yuhongbao_386@hotmail.com>
Cc: "Maciej W. Rozycki" <macro@linux-mips.org>,
Andi Kleen <andi@firstfloor.org>, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: I/O APIC: Timer through 8259A revamp
Date: Thu, 23 Apr 2009 20:04:19 +0200 [thread overview]
Message-ID: <20090423180419.GT13896@one.firstfloor.org> (raw)
In-Reply-To: <fb0aeafb-a24b-413f-8d74-19c28de7faff@u9g2000pre.googlegroups.com>
On Thu, Apr 23, 2009 at 10:45:03AM -0700, yuhong wrote:
> > The new burst of breakage came with the invention of ACPI and its tables
> > for interrupt routing for the APIC.
> Yep, when NVIDIA and ATI entered the chipset market, who would have
> predicted that it would cause more 8254 and APIC related troubles? Or
> it would be years before it were finally fixed properly? Even worse,
> ATI made chipsets before AMD and Intel introduced their 64-bit CPUs,
> yet it was the x86-64 architecture where the attempts to fix the ATI
> APIC 8254 timer issues were going to. Only later when it was finally
> fixed properly was it backported to x86.
I'm not sure what you mean here. The ATI timer fixes were done
on both i386 and x86-64.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2009-04-23 18:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.LVGNb1leZ16O2EUrcLYbCwtL9mc@ifi.uio.no>
[not found] ` <fa.DPrbiibT7M43HJi+nTdM88e1eOQ@ifi.uio.no>
[not found] ` <fa.p4mWFgWCFwhnKR83MseIShfc6uQ@ifi.uio.no>
2009-04-23 17:45 ` yuhong
2009-04-23 18:04 ` Andi Kleen [this message]
2009-04-23 22:04 ` Yuhong Bao
2009-10-03 6:51 ` Yuhong Bao
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=20090423180419.GT13896@one.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 \
--cc=yuhongbao_386@hotmail.com \
/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®