Lines Matching refs:flushing

148     'L1D vulnerable'		      L1D flushing is disabled
191    The conditional mode avoids L1D flushing after VMEXITs which execute
373 		the hypervisors, i.e. unconditional L1D flushing
386 		mitigation, i.e. conditional L1D flushing
395 		i.e. conditional L1D flushing.
410 The default is 'flush'. For details about L1D flushing see :ref:`l1d_flush`.
418 The KVM hypervisor mitigation mechanism, flushing the L1D cache when
462    To avoid the overhead of the default L1D flushing on VMENTER the
463    administrator can disable the flushing via the kernel command line and
475   the kernel, it's only required to enforce L1D flushing on VMENTER.
477   Conditional L1D flushing is the default behaviour and can be tuned. See
484   the system is fully protected. SMT can stay enabled and L1D flushing on
495   - L1D flushing on VMENTER:
497     L1D flushing on VMENTER is the minimal protection requirement, but it
500     Conditional L1D flushing is the default behaviour and can be tuned. See
529     Disabling SMT and enforcing the L1D flushing provides the maximum
533     SMT control and L1D flushing can be tuned by the command line
543     enabled and L1D flushing is not required, but the performance impact is
563    the nested hypervisor; this is a complex operation, and flushing the L1D
568    is an optimization to avoid double L1D flushing.
581   - L1D conditional flushing on VMENTER when EPT is enabled for