Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64 with MCP51 laptops

Hello,

On Tue, 11 Dec 2007 14:16:01 +0100
Rene Herman <rene.herman@xxxxxxxxxxxx> wrote:

On 11-12-07 13:08, David Newall wrote:

Rene Herman wrote:

(*) some local testing shows it to be almost exactly that for both out and
in on my own PC -- a little over. If anyone cares, see attached little test
program. The "little over" I don't worry about. 0 us delay is also fine for
me and if any code was _that_ fragile it would have broken long ago.

Some results :

Core 2Duo 1.73GHz :
[root@tux tmp]# ./in
out = 2366
in = 2496
[root@tux tmp]# ./in
out = 3094
in = 2379

Plain old PIII 600 MHz:
[root@www-dev /tmp]# ./in
out = 314
in = 543
[root@www-dev /tmp]# ./in
out = 319
in = 538
[root@www-dev /tmp]# ./in
out = 319
in = 550
[root@www-dev /tmp]# ./in
out = 329
in = 531

Opteron 150 2.4GHz :
-bash-3.1# ./in
out = 4801
in = 4863
-bash-3.1# ./in
out = 5041
in = 4909
-bash-3.1# ./in
out = 4829
in = 4886

Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Quantcast