I'm talking about hw or kernel/hv level mitigations, even if expensive like only using 1/2 of ram or perf ctr trapping
-
-
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 -
The memory timings can generally be configured via the BIOS/UEFI menus for non-OEM desktops and servers.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker and
There are auto-configuration mechanisms for the memory to provide defaults, but it can be done manually.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker and
It's one of the things that overclockers like to tune for performance but you can also go the other way.
1 reply 0 retweets 0 likes -
Replying to @CopperheadOS @RichFelker and
AFAIK, those timing settings expose the ability to force more frequent refreshes to mitigate rowhammer.
1 reply 1 retweet 0 likes
Whoever writes a howto on making the settings (and avoiding buying boards that don't let you) is a hero.
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.