ir3/sched: Fix could_sched() determination
authorConnor Abbott <cwabbott0@gmail.com>
Fri, 20 May 2022 11:57:23 +0000 (13:57 +0200)
committerMarge Bot <emma+marge@anholt.net>
Wed, 22 Jun 2022 10:09:13 +0000 (10:09 +0000)
commitc601ba332b4a106072cd3315b7886e9937d86212
tree70e58ec307e5b2f9bb17daed21dd11952e6ac7a3
parenta8671b2182b4bfb835355ef383b0ab0293d9462a
ir3/sched: Fix could_sched() determination

This needs to be accurate so that when we split and then schedule a new
a0.x/a1.x/p0.x write we will eventually make progress. It wasn't taking
the kill_path into account which could create an infinite loop as we
keep scheduling writes whose uses are blocked because they are memory
instructions not on the kill_path.

Closes: #6413
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/16635>
src/freedreno/ir3/ir3_sched.c