[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <475EC320.5080008@keyaccess.nl>
Date: Tue, 11 Dec 2007 18:04:32 +0100
From: Rene Herman <rene.herman@...access.nl>
To: "David P. Reed" <dpreed@...d.com>
CC: Andi Kleen <andi@...stfloor.org>,
"linux-os (Dick Johnson)" <linux-os@...logic.com>,
David Newall <david@...idnewall.com>,
Paul Rolland <rol@...917.net>,
"H. Peter Anvin" <hpa@...or.com>, Krzysztof Halasa <khc@...waw.pl>,
Pavel Machek <pavel@....cz>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, rol@...be.net
Subject: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64
with MCP51 laptops
On 11-12-07 18:00, David P. Reed wrote:
> Which port do you want me to test?
Oh, thought your previous reply was already responding to this. The "other
diagnostic port", 0xed. The point is not so much that it's going to be a
good alternate solution but to exclude it being a possible solution.
> Also, I can run the timing test on my machine if you share the source
> code so I can build it.
Thanks, would be interesting. This one:
Rene.
View attachment "port80.c" of type "text/plain" (1680 bytes)
Powered by blists - more mailing lists