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.
[ Parent
| on HN ]