I'm a novice but doesn't this bring back the spectre (ha) of process (or cache?) security concerns that have cropped up with multithreaded approaches in the past years?
I'm not sure "bring back" is the right way to put it: it's been haunting us this whole time.
Getting rid of SMT gives you guarantees that certain resources are separated between software threads. That probably makes it easier for them to focus on making sure that other resources can be shared correctly.
Yeah sorry I didn't mean "bring back" in that its a solved problem, only that I've heard of moving away from SMT (as Intel may be doing here) as one of the best, if hardline, solutions for, at least, some of those concerns. But then the approach the GP quoted seems to step back towards that?
Getting rid of SMT gives you guarantees that certain resources are separated between software threads. That probably makes it easier for them to focus on making sure that other resources can be shared correctly.