Lines Matching refs:mitigation
1640 mitigation.
1647 The mitigation may have a performance impact but can be
1648 disabled. On systems without the microcode mitigation
1649 disabling AVX serves as a mitigation.
1652 microcode mitigation. No effect if the microcode
1653 mitigation is present. Known to cause crashes in
1656 off: Disable GDS mitigation.
2525 Default: enabled on cores which need mitigation.
2680 never: Disables the mitigation
2690 Control mitigation for L1D based snooping vulnerability.
2701 This parameter controls the mitigation. The
2704 on - enable the interface for the mitigation
2706 l1tf= [X86] Control mitigation of the L1TF vulnerability on
2733 hypervisor mitigation, i.e. conditional
2746 hypervisor mitigation.
3069 Control mitigation for the Micro-architectural Data
3081 This parameter controls the MDS mitigation. The
3084 full - Enable MDS mitigation on vulnerable CPUs
3085 full,nosmt - Enable MDS mitigation and disable
3087 off - Unconditionally disable MDS mitigation
3090 an active TAA mitigation as both vulnerabilities are
3092 this mitigation, you need to specify tsx_async_abort=off
3364 [X86,INTEL] Control mitigation for the Processor
3371 Therefore, similar to MDS and TAA, the mitigation
3374 This parameter controls the mitigation. The
3377 full - Enable mitigation on vulnerable CPUs
3379 full,nosmt - Enable mitigation and disable SMT on
3382 off - Unconditionally disable mitigation
3386 MDS or TAA mitigation as these vulnerabilities are
3388 disable this mitigation, you need to specify
5502 retbleed= [X86] Control mitigation of RETBleed (Arbitrary
5512 off - no mitigation
5514 auto,nosmt - automatically select a mitigation,
5516 the full mitigation (only on Zen1
5534 Selecting 'auto' will choose a mitigation method at run
5897 spectre_v2= [X86] Control mitigation of Spectre variant 2
5910 mitigation method at run time according to the
5915 Selecting 'on' will also enable the mitigation
5936 [X86] Control mitigation of Spectre variant 2
5947 but mitigation can be enabled via prctl
5948 per thread. The mitigation control state
5959 threads will enable the mitigation unless
5968 auto - Kernel selects the mitigation depending on
5971 Default mitigation: "prctl"
5977 [X86] Control RAS overflow mitigation on AMD Zen CPUs
5979 off - Disable mitigation
5980 microcode - Enable microcode mitigation only
5981 safe-ret - Enable sw-only safe RET mitigation (default)
5982 ibpb - Enable mitigation by issuing IBPB on
5985 (cloud-specific mitigation)
5988 [HW] Control Speculative Store Bypass (SSB) Disable mitigation
6014 picks the most appropriate mitigation. If the
6016 CPU is vulnerable the default mitigation is
6086 (SRBDS) mitigation.
6098 The microcode mitigation can be disabled with
6101 off: Disable mitigation and remove
6176 firmware based mitigation, this parameter
6177 indicates how the mitigation should be used:
6179 force-on: Unconditionally enable mitigation for
6181 force-off: Unconditionally disable mitigation for
6183 kernel: Always enable mitigation in the
6648 tsx_async_abort= [X86,INTEL] Control mitigation for the TSX Async
6663 This parameter controls the TAA mitigation. The
6666 full - Enable TAA mitigation on vulnerable CPUs
6669 full,nosmt - Enable TAA mitigation and disable SMT on
6673 off - Unconditionally disable TAA mitigation
6676 prevented by an active MDS mitigation as both vulnerabilities
6678 this mitigation, you need to specify mds=off too.
6682 and deploy MDS mitigation, TAA mitigation is not
6684 mitigation.