Lines Matching refs:mitigation

26 Not all processors are affected by all variants of MDS, but the mitigation
103        - The processor is vulnerable, but no mitigation enabled
106          mitigation is enabled on a best effort basis.
109          based mitigation mechanism is not advertised via CPUID, the kernel
110          selects a best effort mitigation mode. This mode invokes the mitigation
119        - The processor is vulnerable and the CPU buffer clearing mitigation is
139 enables the mitigation by default. The mitigation can be controlled at boot
148   The mitigation for MDS clears the affected CPU buffers on return to user
160 Virtualization mitigation
168     If the L1D flush mitigation is enabled and up to date microcode is
169     available, the L1D flush mitigation is automatically protecting the
172     If the L1D flush mitigation is disabled then the MDS mitigation is
173     invoked explicit when the host MDS mitigation is enabled.
181     mitigation is enabled.
233   See the relevant chapter in the L1TF mitigation documentation for details:
254 		CPUs.  This is the complete mitigation.
263 will have no effect as the same mitigation is used for both
273    execute untrusted code which is supplied externally, then the mitigation
288    If the MDS mitigation is enabled and SMT is disabled, guest to host and