On pe, 2017-01-27 at 13:06 +, Chris Wilson wrote:
> A very rare problem we encounter is that as retire the request we find
we -^
> that it appears to not have been yet executed. Other than malevolent hw,
> one possible explanation is that the update of
A very rare problem we encounter is that as retire the request we find
that it appears to not have been yet executed. Other than malevolent hw,
one possible explanation is that the update of the fence status on one
cpu (an atomic_dec_and_test) is not yet visible to the retiree on
another cpu.
