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

[Jiri Kosina <jkosina@suse.cz>]

On Tue, 15 Oct 2019, speck for Michal Hocko wrote:

> From 9666e91b63cd6213d362d04289e1bcbbe2050bc3 Mon Sep 17 00:00:00 2001
> From: Michal Hocko <mhocko@suse.com>
> Date: Tue, 15 Oct 2019 11:21:01 +0200
> Subject: [PATCH] x86, tsx: allow to set tsx=auto by a config option
> 
> There is a general consensus that TSX usage is not largely spread while
> the history shows there is a non trivial space for side channel attacks
> possible. Therefore the tsx is disabled by default even on platforms
> that might have a safe implementation of TSX according to the current
> knowledge. This is a fair trade off to make.
> 
> There are, however, workloads that really do benefit from using TSX and
> updating to a newer kernel with TSX disabled might introduce a
> noticeable regressions. This would be especially a problem for Linux
> distributions which will provide TAA mitigations.
> 
> Introduce X86_INTEL_ENABLE_SAFE_TSX config option to override the
> default tsx=off semantic and make tsx=auto a default which is more
> update friendly.

So given the recent clarifications, especially around older MDS_NO=0 CPUs, 
I think it'd actually make more sense to turn this into a config option 
that would simply allow to chose what the default behavior should be, 
chosing from tristate off/on/auto.

Thanks,

-- 
Jiri Kosina
SUSE Labs