News for hackers. Stuff that matters.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by Roritharr on Thursday August 23, 2018 @03:48PM (#17830147)
The latter question is very important indeed. If you for instance render websites in your vm they, if i understand correctly, can potentially read secrets from other processes, like db credentials and other stuff...

If the only real solution is to turn off HT/SMT that, seen positively, should net us a lot faster VMs then...

Re:Disable SMT/Hyperthreading in all Intel BIOSes by gruez on Thursday August 23, 2018 @04:00PM (#17830261)
>If the only real solution is to turn off HT/SMT that, seen positively, should net us a lot faster VMs then...

you also doubled the cost of each VM (in terms of cpu), but you didn't double the performance of each VM, so it's a net negative.

Re:Disable SMT/Hyperthreading in all Intel BIOSes by Roritharr on Thursday August 23, 2018 @04:06PM (#17830295)
It might be Intel in the end having to pay that cost...
Re:Disable SMT/Hyperthreading in all Intel BIOSes by geofft on Thursday August 23, 2018 @03:50PM (#17830177)
If you render websites that run code in your VM (e.g., you're running a traditional shared hosting infrastructure where mutually-untrusted users can upload PHP scripts, or you're doing something serverless / FaaS / Cloudflare Workers / etc. where mutually-untrusted users can upload functions), then yes. If you're rendering websites in the sense of hosting WordPress for lots of people but not permitting custom plugins, then no.
Re:Disable SMT/Hyperthreading in all Intel BIOSes by Roritharr on Thursday August 23, 2018 @03:53PM (#17830196)
I thought more about Rendering and executing their js for screenshotting purposes for example.