Tweet-sized explanation of Foreshadow: Intel chips with speculative execution erroneously use OS-private bits of not-present page table entries as physical addresses, allow reading L1-cached data from resulting location via timing side-channel.
-
Show this thread
-
There's no way Spectre is going to be fixed without just nuking speculative execution from orbit. It was a bad idea. Go back to 90s-era microarchitectures and start over figuring out how to make it fast.
2 replies 2 retweets 5 likesShow this thread -
Replying to @RichFelker
There is also no way society is going to give up speed gains for the sake of security. As
@securelyfitz put it to me some months back. Spec ex is inherently a side channel; it's bad we took so long to realize it, but we have to live with it if we want forward progress.3 replies 0 retweets 0 likes -
Replying to @cr1901 @securelyfitz
"Society" largely does not care about speed. Machines 10-15 years ago were plenty fast for ordinary stuff ppl want to do, except hardcore gaming. In server space it's kinda different, but only because ppl adjust their tooling to what the cpu can handle (or what they can afford).
1 reply 0 retweets 0 likes -
Replying to @RichFelker @securelyfitz
Compiling? Bad enough LLVM/Clang takes 20 minutes using 8 threads of Skylake. IME, Something that takes 3 minutes using 8 threads of Skylake takes a few hours on 1 thread of 2007 Atom Netbook...
1 reply 0 retweets 0 likes -
Replying to @cr1901 @securelyfitz
Compiling is not something "society" does. It's something we weird people do. ;-)
1 reply 0 retweets 0 likes
But my S1260 is only something like 2-3x slower than the i7-6600U I replaced with it. GCC builds aren't fast, but not painfully slow either.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.