Crossing the Hyper-Thread Boundary
Blog post from exe.dev
Modern CPUs use hyper-threading to run separate programs on two logical cores within one physical core, improving efficiency but creating potential transient-execution security risks such as MDS, where one workload could extract data from another. To protect virtual machines hosted for different exe.dev users, Linux core scheduling cookies restrict which processes may share a physical core. Rather than assigning every VM a unique cookie, which reduces hardware efficiency, exe.dev assigns a shared cookie to VMs within the same team, preventing VMs belonging to different teams or ungrouped users from running on the same core. This model assumes team members trust one another, while administrators of teams requiring stronger isolation can disable core sharing through the team settings command; unaffiliated VMs currently remain isolated from all other VMs by default.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.