There are lots of things browsers can do to mitigate this, but it requires a change from the simplistic worldview of trusting a random websites javascript and a

There are lots of things browsers can do to mitigate this, but it requires a change from the simplistic worldview of trusting a random websites javascript and assuming a software emulator won't reveal information about the host. If this paper finally prompts more concern about side channel attacks that would be great. Thing they could do include: - running the javascript engine on a specific core and evicting other processes from that core, which is a common technique in real time systems (pinning and isolating); - hardware cache partitioning, then locking PTEs and TLBs for that core (eg Intel xCAT); - separate websites by levels of trust, and run less trusted code more conservatively. Time monotonicity can be preserved without enabling high resolution linearity. (Intel CAT hasn't made it to the kernel mainline yet, nearly though. https://github.com/01org/intel-cmt-cat https://github.com/01org/intel-cmt-cat )