News for hackers. Stuff that matters.
Re:A tale of an impossible bug: big.LITTLE and caching by cesarb on Tuesday September 13, 2016 @07:47AM (#12487182)
Perhaps a better (and simpler) workaround, then, could be to clamp the reported cache line size to 64 bytes. So even if the Samsung core reports 128-byte cache lines, the code would simply invalidate each line twice, and if it is migrated in the middle of the invalidation loop, it would still work correctly.
Re:A tale of an impossible bug: big.LITTLE and caching by gcp on Tuesday September 13, 2016 @07:59AM (#12487291)
This is exactly the fix used in the kernel, yes. The trickiness and complexity comes from the cache line size probe having to be intercepted.