Another issue caused by hyperthreading. It's starting to look more and more like the OpenBSD guys made the right choice by turning it off. At this point, I th

Another issue caused by hyperthreading. It's starting to look more and more like the OpenBSD guys made the right choice by turning it off. At this point, I think the only other option is for OS guys to implement some kind of security-aware scheduler, where threads can request secure execution on a dedicated processor. Though I suppose it might make more sense to execute on isolated processors by default and have threads explicitly permit unsecured execution for non-critical stuff.