Lines Matching full:mitigation

2231 			Default: enabled on cores which need mitigation.
2320 	kvm-intel.vmentry_l1d_flush=[KVM,Intel] Mitigation for L1 Terminal Fault
2328 			never:	Disables the mitigation
2336 	l1tf=           [X86] Control mitigation of the L1TF vulnerability on
2363 				hypervisor mitigation, i.e. conditional
2376 				hypervisor mitigation.
2655 			Control mitigation for the Micro-architectural Data
2667 			This parameter controls the MDS mitigation. The
2670 			full       - Enable MDS mitigation on vulnerable CPUs
2671 			full,nosmt - Enable MDS mitigation and disable
2673 			off        - Unconditionally disable MDS mitigation
2676 			an active TAA mitigation as both vulnerabilities are
2678 			this mitigation, you need to specify tsx_async_abort=off
2909 			[X86,INTEL] Control mitigation for the Processor
2916 			Therefore, similar to MDS and TAA, the mitigation
2919 			This parameter controls the mitigation. The
2922 			full       - Enable mitigation on vulnerable CPUs
2924 			full,nosmt - Enable mitigation and disable SMT on
2927 			off        - Unconditionally disable mitigation
2931 			MDS or TAA mitigation as these vulnerabilities are
2933 			disable this mitigation, you need to specify
4654 	retbleed=	[X86] Control mitigation of RETBleed (Arbitrary
4658 			off          - no mitigation
4660 			auto,nosmt   - automatically select a mitigation,
4662 				       the full mitigation (only on Zen1
4673 			Selecting 'auto' will choose a mitigation method at run
4994 	spectre_v2=	[X86] Control mitigation of Spectre variant 2
5007 			mitigation method at run time according to the
5012 			Selecting 'on' will also enable the mitigation
5033 			[X86] Control mitigation of Spectre variant 2
5044 				  but mitigation can be enabled via prctl
5045 				  per thread.  The mitigation control state
5056 				  threads will enable the mitigation unless
5065 			auto    - Kernel selects the mitigation depending on
5068 			Default mitigation:
5075 			[HW] Control Speculative Store Bypass (SSB) Disable mitigation
5101 				  picks the most appropriate mitigation. If the
5103 				  CPU is vulnerable the default mitigation is
5155 			(SRBDS) mitigation.
5167 			The microcode mitigation can be disabled with
5170 			off:    Disable mitigation and remove
5195 			firmware based mitigation, this parameter
5196 			indicates how the mitigation should be used:
5198 			force-on:  Unconditionally enable mitigation for
5200 			force-off: Unconditionally disable mitigation for
5202 			kernel:    Always enable mitigation in the
5534 	tsx_async_abort= [X86,INTEL] Control mitigation for the TSX Async
5549 			This parameter controls the TAA mitigation.  The
5552 			full       - Enable TAA mitigation on vulnerable CPUs
5555 			full,nosmt - Enable TAA mitigation and disable SMT on
5559 			off        - Unconditionally disable TAA mitigation
5562 			prevented by an active MDS mitigation as both vulnerabilities
5564 			this mitigation, you need to specify mds=off too.
5568 			and deploy MDS mitigation, TAA mitigation is not
5570 			mitigation.