It does when the attack mechanism is a completely standard attack (cache eviction on aes tables) with an established solution (not running aes on shared resourc

It does when the attack mechanism is a completely standard attack (cache eviction on aes tables) with an established solution (not running aes on shared resources, various masking operations, or simply doing the correct thing and using the system aes implementation or hardware). This attack is not wholly different from them saying “we made an aes implementation on the gpu and it leaked timing information”, yes it’s technically present, but the problem is not that you can’t tell the gpu to disable any predictors or caches, it’s that you’re using a wholly unsuited tool for a wholly inappropriate task with known hazards and expecting different outcome.