@Kensan I confess to liking @csirac2’s work in listing precursor papers a lot. Now they are all backslapping each other on the birdsite about their brilliance and/or how they always knew and/or other assorted noise.
My only question is why blow it out of all proportion? Yes, if you have VMs it is a real bummer but, objectively, VM security has always been a matter of faith rather than technology (exception LPARs). I believe @mulander mentioned Theo’s VM rant from 2007. Spot on.
@cynicalsecurity @mulander @csirac2 What I like about the issues is that they illustrate design flaws independent of the maker even though everybody is caught up on Intel. I find the technical side of the attacks interesting but then again they fall right into my area of interest. That being said, I am sure there are other bugs released in the meantime which are more relevant to end users.
@Kensan @csirac2 @mulander My confusion was always around this idea that somehow it was “two cores for the price of one” where clearly it could not be the case: there was still only one execution unit so you now had on-core multitasking managed by…
microcode! The feeling was always “this cannot work properly” not to mention the “why would I want to do that?”
I’d love a good technical explanation as to why but all I can think of is “marketing solution by the microcode group”.
@csirac2 @mulander @cynicalsecurity However it is apparent that so many more resources are shared between logical cores than physical cores that it is bound to be problematic in so many use cases. At least with HT there is a way to choose not to go down this path and choose a different tradeoff by disabling HT cores. This spares us a lot of complexity.
@cynicalsecurity @mulander @csirac2 Not wanting to appear like bashing Linux as I am sure there a other motivations/good reasons and they make different tradeoffs but as an illustration: it even has a HT-aware scheduler so the complexity is rooted in the Hardware feature and all users are paying for it. ¯\_(ツ)_/¯
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!