linux-kernel - Re: I/O APIC: Timer through 8259A revamp

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090423180419.GT13896@one.firstfloor.org>
Date:	Thu, 23 Apr 2009 20:04:19 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	yuhong <yuhongbao_386@...mail.com>
Cc:	"Maciej W. Rozycki" <macro@...ux-mips.org>,
	Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: I/O APIC: Timer through 8259A revamp

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@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/