Am 03.08.2018 um 05:10 schrieb Dave Airlie: > From: Dave Airlie <airl...@redhat.com> > > This fixes some hangs with the arb_shader_image_load_store-atomicity tests > on evergreen/cayman GPUs. > > I'm not 100% sure why (VPM hurts my brain), I'm running some piglit > runs to see if it has any bad side effects. > --- > src/gallium/drivers/r600/r600_shader.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/src/gallium/drivers/r600/r600_shader.c > b/src/gallium/drivers/r600/r600_shader.c > index 2229dc8fab3..1341bf2c48c 100644 > --- a/src/gallium/drivers/r600/r600_shader.c > +++ b/src/gallium/drivers/r600/r600_shader.c > @@ -10587,7 +10587,7 @@ static int tgsi_bgnloop(struct r600_shader_ctx *ctx) > /* LOOP_START_DX10 ignores the LOOP_CONFIG* registers, so it is not > * limited to 4096 iterations, like the other LOOP_* instructions. */ > r600_bytecode_add_cfinst(ctx->bc, CF_OP_LOOP_START_DX10); > - > + ctx->bc->cf_last->vpm = 1; > fc_pushlevel(ctx, FC_LOOP); > > /* check stack depth */ >
I think you might get incorrect derivatives afterwards (if some pixels in a quad were invalid)? Or are the lanes in the alu still active (I don't really understand all the vpm stuff...) afterwards? I'm wondering if the tests are just bad? You can get lockups rather easily if you're not extra careful with atomics in loops (because the result of the atomic is undefined for helper invocations, and the hw will never store the result). There was recently some discussion about this on mesa-dev, also see https://bugs.freedesktop.org/show_bug.cgi?id=106902 Roland _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
