[MODERATED] Re: [PATCH v5 08/11] TAAv5 8

On Tue, 2019-10-15 at 18:12 -0500, speck for Josh Poimboeuf wrote:
> On Tue, Oct 15, 2019 at 11:14:03PM +0200, speck for Jiri Kosina wrote:
[...]
> > OK, that piece of information finally made it to make sense again :)
> > 
> > So I believe distros still want the option (Michal's patch) to default to 
> > 'auto', so that actual heavy users of TSX will get the right thing once 
> > they update their CPUs to !TAA_BUG ones, but it's less urgent that I 
> > originally thought.
> 
> So if I understand correctly, you're postulating that distros want:
> 
> a) TAA_BUG && MDS_NO=0 => TSX on
> b) TAA_BUG && MDS_NO=1 => TSX off
> c) !TAA_BUG            => TSX on
[...]

I think this should be:

a) TAA_BUG && MD_CLEAR=1 => TSX on
b) TAA_BUG && MD_CLEAR=0 => TSX off
c) !TAA_BUG              => TSX on

As I understand it, with currently released microcode, no CPUs have
both MDS_NO and MD_CLEAR set.  But with the pending microcode updates,
CPUs with MDS_NO=1 will also get MD_CLEAR=1 and we can use VERW to
mitigate against TAA.

Ben.

-- 
Ben Hutchings
It's easier to fight for one's principles than to live up to them.

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEErCspvTSmr92z9o8157/I7JWGEQkFAl2pEpkACgkQ57/I7JWG
EQkA1w//SzCwH7ZsogvYWJaKWCE0sd/a6OufKYEmpuoDjX9ZgGclNSodETXRkkr5
I5NRUh07ncELDrohVsbUmry7ypEbpl+L0zffe9jrv/WVpqWyXbLt32E6P5bPlZTt
gnDmSlQqB1QnM9SmkYYjK55rSQE2RnVMzXU8VpOklKmcT1sKucpVww+EBkM7jdnF
upk51ronYtwTrzGOHaiZE1x0jinkvJ23XW4ty5LeiULaGCLXVCo0KJzqekdvDMcg
mPL8IrNmIOx0QNTorUkK4FkjX6SBEfj3wpMBLD5SFKX2jnT18tczFifJIPPAMK3G
uiXI0/e+sjhGJMczUwMSnF/H8XdLW6T+o3lkHKmDvfSt2U4bBrohGJx0UKnRY3VX
6sWbbti+zbX5DhlLPQZ+ywvWdESHk9mT8onqjJrxFAAZfgTTNjtPhgjjE817Du8M
+0LPFjiofCxq2Dxh7Aa8HkpNHoW2OVJng9jGaObJl0Q5V8xxyWRvmbqvLt1FXRBi
6fsaTbaSkanSia1nXN0YyNzLGeIXHKMVzBrG8+0X76RYwuPAK46KAdBQMNuWvAZw
9xQVqSazELmQ/YOo0StAXiqu037n6GzqnfJSBVGJwIPrsLMitt0EKRE2SG730hj3
ZqPxY4zojSUfaq7ih7sXOjT0pqlqoQs/7IyCSe+gkT+N1jg0khQ=
=XVvv
-----END PGP SIGNATURE-----