Lines Matching full:safe

58  * 'Vulnerable: Safe RET, no microcode':
60    The "Safe RET" mitigation (see below) has been applied to protect the
64  * 'Vulnerable: Microcode, no safe RET':
85  * 'Mitigation: Safe RET':
91    Selected by default or by spec_rstack_overflow=safe-ret
95    Similar protection as "safe RET" above but employs an IBPB barrier on
123 default one is 'Mitigation: safe RET' which should take care of most
132 As one can surmise, 'Mitigation: safe RET' does come at the cost of some
142 Mitigation: Safe RET
148 the CPU to mispredict every function return using a 'safe return'
152 safe return sequence is itself free from attacker interference.  In Zen3
154 untraining function srso_alias_untrain_ret() and the safe return
156 poisoned BTB entry and using that safe one for all function returns.
162 Checking the safe RET mitigation actually works
165 In case one wants to validate whether the SRSO safe RET mitigation works