On Friday 27 Nov 2020 at 17:14:11 (+0000), Marc Zyngier wrote:
Yeah, the sanitized read feels better, if only because that is
what we are going to read in all the valid cases, unfortunately.
read_sanitised_ftr_reg() is sadly not designed to be called on
a fast path, meaning that 32bit guests will do a bsearch() on
the ID-regs every time they exit...
I guess we will have to evaluate how much we loose with this.
Could we use the trick we have for arm64_ftr_reg_ctrel0 to speed this
up?