Lines Matching refs:safe

64  * 'Vulnerable: Microcode, no 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
115    not affected anymore and thus "safe RET" is not needed.
136 default one is 'Mitigation: safe RET' which should take care of most
145 As one can surmise, 'Mitigation: safe RET' does come at the cost of some
161 the CPU to mispredict every function return using a 'safe return'
165 safe return sequence is itself free from attacker interference.  In Zen3
167 untraining function srso_alias_untrain_ret() and the safe return
169 poisoned BTB entry and using that safe one for all function returns.
175 Checking the safe RET mitigation actually works
178 In case one wants to validate whether the SRSO safe RET mitigation works