Lines Matching full:mitigation

29 Without mitigation, GDS can infer stale data across virtually all
38 Because of this, it is important to ensure that the mitigation stays enabled in
41 The hardware enforces the mitigation for SGX. Likewise, VMMs should  ensure
42 that guests are not allowed to disable the GDS mitigation. If a host erred and
43 allowed this, a guest could theoretically disable GDS mitigation, mount an
46 Mitigation mechanism
53                                           and mitigation support.
55  IA32_MCU_OPT_CTRL[GDS_MITG_DIS]    R/W   Disables the mitigation
71 Mitigation control on the kernel command line
73 The mitigation can be disabled by setting "gather_data_sampling=off" or
75 to the mitigation being enabled. Specifying "gather_data_sampling=force" will
76 use the microcode mitigation when available or disable AVX on affected systems
77 where the microcode hasn't been updated to include the mitigation.
90  Vulnerable                     Processor vulnerable and mitigation disabled.
92                                 mitigation.
93  Mitigation: AVX disabled,
95                                 mitigation. AVX disabled as mitigation.
96  Mitigation: Microcode          Processor is vulnerable and mitigation is in
98  Mitigation: Microcode (locked) Processor is vulnerable and mitigation is in
106 GDS Default mitigation
108 The updated microcode will enable the mitigation by default. The kernel's
109 default action is to leave the mitigation enabled.