From the Wikipedia article on memory refresh [0] for DRAM describing distributed refresh techniques: "For example, the current generation of chips (DDR SDRAM)

From the Wikipedia article on memory refresh [0] for DRAM describing distributed refresh techniques: "For example, the current generation of chips (DDR SDRAM) has a refresh time of 64 ms and 8,192 rows, so the refresh cycle interval is 7.8 μs." Sounds like your idea is already a thing! That's cool! Unfortunately it seems like the performance-cycle period tradeoff is difficult and Rowhammer is taking advantage of that. Protecting subsets of memory is an interesting idea but what bits do you choose? What if I could Rowhammer the memory frame behind a COW page belonging to a setuid binary? I feel like it might be an all or nothing kind of thing in this situation. Who knows though, maybe there's merit in specifically protecting kernel owned frames, it's difficult to say for sure. 0 - https://en.m.wikipedia.org/wiki/Memory_refresh https://en.m.wikipedia.org/wiki/Memory_refresh