3 ms·
Could it have anything to do with the Portsmash attack against hyperthreaded systems? I'm not current on this one, but I recall when it first came out that dis
by SkyMarshal 5y ago
Could it have anything to do with the Portsmash attack against hyperthreaded systems?
I'm not current on this one, but I recall when it first came out that disabling hyperthreading was the only solution.
Has it been solved yet, or are some chipmakers avoiding enabling hyperthreading now as a result?
https://nvd.nist.gov/vuln/detail/CVE-2018-5407 https://nvd.nist.gov/vuln/detail/CVE-2018-5407
- dragontamer 5y agoI doubt it. Otherwise, they would have disabled SMT / Hyperthreading on E1 cores. That's the confusing thing: they have the tech on one core, but not the other.