freedreno/crashdec: Fix apparent off-by-one with ROQ size
authorConnor Abbott <cwabbott0@gmail.com>
Mon, 17 Oct 2022 16:39:16 +0000 (18:39 +0200)
committerMarge Bot <emma+marge@anholt.net>
Thu, 23 Feb 2023 20:02:26 +0000 (20:02 +0000)
commit4060cf5772c1a1cd5dfc988d831ed63802d7db2c
tree09d45295c06fb403a681805d4fa027083e80d4f5
parentce7225c0f90abacc8dfc22d08d2a95cdde2d81cc
freedreno/crashdec: Fix apparent off-by-one with ROQ size

I have multiple examples where this register is too large by one
when comparing to the ROQ read/write pointers in CP_ROQ_*_STAT and the
ROQ data itself, as if it includes the dword most recently read too. I
have an example where it's off by 2 compared to the read pointer, but
the read pointer is also off by 1 itself judging by the SQE program
counter, so that may just be them not getting synchronized. This
off-by-one was getting in the way of figuring out exactly IB2 was being
processed in the next commit.

Signed-off-by: Rob Clark <robdclark@chromium.org>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19551>
src/freedreno/.gitlab-ci/reference/crash.log
src/freedreno/decode/crashdec.c