linux-kernel - Re: [PATCH] x86: Use clflush() instead of wbinvd() whenever possible when changing mapping

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:	Fri, 24 Jul 2009 15:16:49 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Thomas Hellstrom <thellstrom@...are.com>
Cc:	Andi Kleen <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"mingo@...e.hu" <mingo@...e.hu>,
	"venkatesh.pallipadi@...el.com" <venkatesh.pallipadi@...el.com>
Subject: Re: [PATCH] x86: Use clflush() instead of wbinvd() whenever
	possible when changing mapping

> No. It was motivated by the assumption that wbinvd() is just bad:

Ok, got it now.

> Qoute:
>
> WBINVD is a very nasty operation. I was talking to some CPU people and they 
> really recommended to get rid of it as far as possible. Stopping the CPU 
> for msecs is just wrong and there are apparently even some theoretical live 
> lock situations. - It is not interruptible in earlier VT versions and 
> messes up real time in the hypervisor. Some people were doing KVM on rt 
> kernels and had latency spikes from that.
>
>
> /Qoute
> (I believe you wrote that ?)

Yes. That's still true and that's one reason to not use it.

-Andi
--
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/