So the #meldown steps are:
1. Load a byte of memory from kernel. This crashes.
2. Use that byte to load one of 256 cache-lines. This happens before the crash is registered, so while the data is discarded, the data is still cached.
3. Measure which of the 256 cache-lines are fast
-
-
FWIW, "load one of 256 cachelines" never worked quite right for me, although maybe I was just missing something - always just mapping to one of two cachelines worked better
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.