3 ms·
See my second message (next to yours), it's not just that, yes he thinks and clearly says that thissolution is terrible but that's not why he calls them out to
by nolok 9y ago
See my second message (next to yours), it's not just that, yes he thinks and clearly says that thissolution is terrible but that's not why he calls them out to be basically liars; this one is because they put useless filler garbage code all around to hide what's happening in their patches.
I think we're lucky to have someone as clear, outspoken and refusing such crap in charge of the kernel.
- cthalupa 9y agoPart of the problem is Linus doesn't actually understand the different portions of what Intel is doing, and is mixing up IBPB and IBRS. They do different things, and he's thinking they're all part of the same thing. This could be a sign that these things are poorly written and need to be refactored into something more obvious, or it could be that they're so fundamentally complex that it's going to be difficult to grasp without context.
- wtetzner 9y ago> or it could be that they're so fundamentally complex that it's going to be difficult to grasp without context. If it is that fundamentally complex, then it sounds like they need to find a better solution.
- cthalupa 9y agoI don't disagree, but they are working under a time crunch trying to fix something that is a flaw fundamental to modern chip design. Hopefully the goal here is to get everything to a secure state, with time to iterate and improve once everyone can sit back and breathe. Hopefully.