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

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]

Date:	Mon, 10 Dec 2007 05:17:27 +0100
From:	Rene Herman <rene.herman@...access.nl>
To:	Pavel Machek <pavel@....cz>
CC:	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>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: RFC: outb 0x80 in inb_p, outb_p harmful on some modern AMD64
 with MCP51 laptops

On 09-12-07 22:25, Pavel Machek wrote:

> On Sun 2007-12-09 17:59:08, Andi Kleen wrote:

>> Yes, i guess switching to udelay at least on newer systems would
>> be a good idea.  I'm not quite sure about systems without TSC though.
> 
> Something like this? (Warning, will not probably even compile on
> x86-64, I do not have 64-bit compiler near me).

>  static inline void native_io_delay(void)
>  {
> -	asm volatile("outb %%al,$0x80" : : : "memory");
> +	udelay(8);
>  }

Alan, did you double-check that 8 us? I tried to but I seem to not have 
trustworthy documentation.

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/