[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <475EBD69.9090709@keyaccess.nl>
Date: Tue, 11 Dec 2007 17:40:09 +0100
From: Rene Herman <rene.herman@...access.nl>
To: John Stoffel <john@...ffel.org>
CC: Paul Rolland <rol@...917.net>,
David Newall <david@...idnewall.com>,
"H. Peter Anvin" <hpa@...or.com>, Krzysztof Halasa <khc@...waw.pl>,
Pavel Machek <pavel@....cz>, Andi Kleen <andi@...stfloor.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
"David P. Reed" <dpreed@...d.com>, 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 17:32, John Stoffel wrote:
> Here's my results on a PIII Xeon, 550mhz, 440GX chipset, and an ISA
> slot, which until recently was actually used with an 8 port serial
> card:
>
> jfsnew:~/src> sudo ./port80
> out: 729
> in : 348
> jfsnew:~/src> sudo ./port80
> out: 729
> in : 354
> jfsnew:~/src> sudo ./port80
> out: 729
> in : 350
> jfsnew:~/src> sudo ./port80
> out: 728
> in : 346
> jfsnew:~/src> sudo ./port80
> out: 730
> in : 340
Thank you. That's a little odd. The "in" time should be close to the "out"
time really.
Well, err, <shrug> I guess.
For now noone's contemplating replacing the out with an in anyways :-)
Rene.
--
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/
Powered by blists - more mailing lists