Lines Matching refs:mitigation

99 …- The CPU is affected by this vulnerability and the microcode and kernel mitigation are not applie…
102        mitigation is enabled on a best effort basis.
105        based mitigation mechanism is not advertised via CPUID, the kernel
106        selects a best effort mitigation mode. This mode invokes the mitigation
126 enables the mitigation by default.
129 The mitigation can be controlled at boot time via a kernel command line option.
132 Virtualization mitigation
152   off		This option disables the TAA mitigation on affected platforms.
156   full	        TAA mitigation is enabled. If TSX is enabled, on an affected
158                 systems which are MDS-affected and deploy MDS mitigation,
164                 mitigation. When TSX is disabled, SMT is not disabled because
171 effect as the same mitigation is used for both vulnerabilities.
224 For the affected platforms below table indicates the mitigation status for the
247 untrusted code which is supplied externally, then the mitigation can be
260 explicitly enable the mitigation.
270   - Deploy TSX disable mitigation (tsx_async_abort=full tsx=off).