Guess we know the answer to this now (thanks to https://www.usenix.org/system/files/conference/usenixsecurity16/sec16_paper_razavi.pdf …) You should disable Memory Deduplication.https://twitter.com/haroonmeer/status/579229248914898944 …
-
-
Replying to @haroonmeer @thegrugq
Or fix rowhammer already. WHY is there still no literature on actually fixing it??
1 reply 0 retweets 0 likes -
I'm talking about hw or kernel/hv level mitigations, even if expensive like only using 1/2 of ram or perf ctr trapping
1 reply 0 retweets 0 likes -
Replying to @RichFelker @haroonmeer
I think Intel is massively opposed to dealing with it
1 reply 0 retweets 0 likes -
Replying to @thegrugq @haroonmeer
Is there a reason? Denial in hopes they don't get sued and forced to replace every chipset out there?
1 reply 0 retweets 0 likes -
Seems like the existence of viable workarounds would help reduce that risk if anything.
1 reply 0 retweets 0 likes -
Can it be mitigated with conservative timings for the memory controller rather than auto-detected ones?
1 reply 0 retweets 0 likes -
Have you ever seen a list of boards where timings are programmable, tools needed, safe values to set?
2 replies 0 retweets 0 likes
This is what I mean by complete lack of literature on defense against rowhammer.
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.