Comment # 8 on bug 1201665 from Michal Hocko

(In reply to Ralf K���lmel from comment #7)
> (In reply to Borislav Petkov from comment #6)
> > (In reply to Ralf K���lmel from comment #5)
> > 
> > You can boot with mitigations=off and use that as the baseline for your
> > measurements. The overhead of the return thunks which are part of retbleed
> > is ~1% but that doesn't matter if you use this configuration as your
> > baseline.
> It would be good to have such a baseline, but we haven't it yet and
> recomputations are time-consuming.

This is really unfortunate but please consider that our top priority is to
stabilize all the code streams. You can imagine that disruptive change like
Retbleed mitigation is rather subtle and it can blow up easily. 

Saying that we might consider full retbleed disabling (including return thunks)
later on but this is not the top priority at the moment.