3 ms·
I'm going to assume that somewhere in the code was something like if(flags | PREFETCH_EX) { xdcbt } else { safe way } And the br
by Gibbon1 9y ago
I'm going to assume that somewhere in the code was something like
if(flags | PREFETCH_EX)
{
xdcbt
}
else
{
safe way
}
And the branch predictor would decide the xdcbt branch was most likely, executes xdcbt and then realizes oops and does it the safe way. Which would be okay except xdcbt is evil, it breaks cache coherency.
- unwind 9y agoNitpick: you meant & for a bitwise AND, of course.
- djhworld 9y agoWow, interesting to see feature flags causing this undesired effect!
- syncsynchalt 9y agoAny if statement could cause this, doesn't have to be feature flags. An untrained branch predictor could still take the "wrong" path even if none of the code that calls that if statement takes the bad path. That's presumably what happened here, the calling program removed all instances of PREFETCH_EX but the CPU would still sometimes execute that branch, such as on the first run through that function. This is a lot like the problem of "don't think of a pink elephant". The mere existence of the "evil opcode" in the library means the CPU might execute it under certain circumstances.