[PATCH] drm/msm/a6xx+: Insert a fence wait before SMMU table update
Rob Clark
robdclark at gmail.com
Tue Sep 17 15:30:25 UTC 2024
On Tue, Sep 17, 2024 at 6:47 AM Konrad Dybcio <konradybcio at kernel.org> wrote:
>
> On 13.09.2024 9:51 PM, Rob Clark wrote:
> > From: Rob Clark <robdclark at chromium.org>
> >
> > The CP_SMMU_TABLE_UPDATE _should_ be waiting for idle, but on some
> > devices (x1-85, possibly others), it seems to pass that barrier while
> > there are still things in the event completion FIFO waiting to be
> > written back to memory.
>
> Can we try to force-fault around here on other GPUs and perhaps
> limit this workaround?
not sure what you mean by "force-fault"... we could probably limit
this to certain GPUs, the only reason I didn't is (a) it should be
harmless when it is not needed, and (b) I have no real good way to get
an exhaustive list of where it is needed. Maybe/hopefully it is only
x1-85, but idk.
It does bring up an interesting question about preemption, though
BR,
-R
> Akhil, do we have any insight on this?
>
> Konrad
More information about the dri-devel
mailing list