News for hackers. Stuff that matters.

A comment on OpenBSD chief de Raadt says no easy fix for new Intel CPU bug. Parent comment

Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by pas on Monday June 25, 2018 @05:51AM (#17391100)
If you pin VMs to different cores, never sharing hyperthreads, then the risk is contained per VM (or per core).
[ Parent | on HN ]
Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by pabloski on Monday June 25, 2018 @06:26AM (#17391233)
Let's hope there's no inter-core side-channel lurking in the shadows :(

It is time to rethinking the engineering methodologies we use in the electronics/informatics field.

[ Parent | on HN ]
Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by cm2187 on Monday June 25, 2018 @06:32AM (#17391259)
Breaking x86 backward compatibility? That would be fun.
[ Parent | on HN ]
Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by pabloski on Monday June 25, 2018 @10:27AM (#17392664)
So we are between a rock and a hard place.
[ Parent | on HN ]
Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by pocak on Monday June 25, 2018 @09:12AM (#17392101)
If you give two threads on one core to one VM, the VM could attack the hypervisor. It could have one thread run the TLB probe loop while the other does something that's handled by the hypervisor.
[ Parent | on HN ]
Re:OpenBSD chief de Raadt says no easy fix for new Intel CPU... by AlphaSite on Monday June 25, 2018 @10:48AM (#17392811)
Isn’t there typically a VMM per VM? So the risk is then lower?

http://3.bp.blogspot.com/-OyjQUpLowmg/Udz1_NxqNLI/AAAAAAAABV...

[ Parent | on HN ]