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
107          The mitigation is enabled on a best effort basis. See :ref:`vmwerv`
109        - The processor is vulnerable and the CPU buffer clearing mitigation is
124 Best effort mitigation mode
128   mitigation mechanism is not advertised via CPUID the kernel selects a best
129   effort mitigation mode.  This mode invokes the mitigation instructions
147 enables the mitigation by default. The mitigation can be controlled at boot
156   The mitigation for MDS clears the affected CPU buffers on return to user
168 Virtualization mitigation
176     If the L1D flush mitigation is enabled and up to date microcode is
177     available, the L1D flush mitigation is automatically protecting the
180     If the L1D flush mitigation is disabled then the MDS mitigation is
181     invoked explicit when the host MDS mitigation is enabled.
189     mitigation is enabled.
241   See the relevant chapter in the L1TF mitigation documentation for details:
262 		CPUs.  This is the complete mitigation.
271 will have no effect as the same mitigation is used for both
281    execute untrusted code which is supplied externally, then the mitigation
296    If the MDS mitigation is enabled and SMT is disabled, guest to host and