linux-kernel - intel_i830_chipset_flush(): local clflush() vs. global wbinvd()

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-next>] [day] [month] [year] [list]

Message-Id: <4BD5787C020000780003C1DB@vpn.id2.novell.com>
Date:	Mon, 26 Apr 2010 10:26:52 +0100
From:	"Jan Beulich" <JBeulich@...ell.com>
To:	<eric@...olt.net>, <Brice.Goglin@...-lyon.org>
Cc:	<linux-kernel@...r.kernel.org>
Subject: intel_i830_chipset_flush(): local clflush() vs. global
	 wbinvd()

Eric, Brice,

what is the point of issuing wbinvd() on all CPUs here if clflush isn't
available, but using clflush() (if available) only on the current CPU?

Thanks, Jan

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