Lines Matching full:mitigation

10 provided to untrusted guests may need mitigation. These vulnerabilities are
13 by an unmitigated transient execution attack. Mitigation for these
110 section, mitigation largely remains the same for all the variants, i.e. to
117 specific variants of Processor MMIO Stale Data vulnerabilities and mitigation
150 Mitigation  chapter
153 same mitigation strategy to force the CPU to clear the affected buffers before
166 additional mitigation is needed on such CPUs.
168 For CPUs not affected by MDS or TAA, mitigation is needed only for the attacker
173 Mitigation points
177 Same mitigation as MDS when affected by MDS/TAA, otherwise no mitigation
188 Same mitigation as MDS when processor is also affected by MDS/TAA, otherwise
193 Mitigation control on the kernel command line
200   full        If the CPU is vulnerable, enable mitigation; CPU buffer clearing
204               complete mitigation.
205   off         Disables mitigation completely.
209 command line, then the kernel selects the appropriate mitigation.
211 Mitigation status information
226        - The processor is vulnerable, but no mitigation enabled
229          mitigation is enabled on a best effort basis.
232          based mitigation mechanism is not advertised via CPUID, the kernel
233          selects a best effort mitigation mode. This mode invokes the mitigation
241      * - 'Mitigation: Clear CPU buffers'
242        - The processor is vulnerable and the CPU buffer clearing mitigation is
246 	 out of Servicing period. Mitigation is not attempted.