Lines Matching full:flushing

148     'L1D vulnerable'		      L1D flushing is disabled
176    Flushing the L1D evicts not only the data which should not be accessed
178    data. Flushing the L1D has a performance impact as the processor has to
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.
413 The default is 'flush'. For details about L1D flushing see :ref:`l1d_flush`.
421 The KVM hypervisor mitigation mechanism, flushing the L1D cache when
466    To avoid the overhead of the default L1D flushing on VMENTER the
467    administrator can disable the flushing via the kernel command line and
479   the kernel, it's only required to enforce L1D flushing on VMENTER.
481   Conditional L1D flushing is the default behaviour and can be tuned. See
488   the system is fully protected. SMT can stay enabled and L1D flushing on
499   - L1D flushing on VMENTER:
501     L1D flushing on VMENTER is the minimal protection requirement, but it
504     Conditional L1D flushing is the default behaviour and can be tuned. See
533     Disabling SMT and enforcing the L1D flushing provides the maximum
537     SMT control and L1D flushing can be tuned by the command line
547     enabled and L1D flushing is not required, but the performance impact is
567    the nested hypervisor; this is a complex operation, and flushing the L1D
572    is an optimization to avoid double L1D flushing.
586   - L1D conditional flushing on VMENTER when EPT is enabled for