From 962a09c90f30b1fe347aebf6996548ee6b355326 Mon Sep 17 00:00:00 2001 From: Karol Herbst Date: Sat, 3 Jul 2021 10:01:52 +0200 Subject: [PATCH] nv50: remove nv50_bufctx_fence call in vbo_kick_notify No idea why it is there. nvc0 doesn't do anything like it and it doesn't regress any tests. Also removing is easier than handling the fence locking inside the kick notify handler. Signed-off-by: Karol Herbst Part-of: --- src/gallium/drivers/nouveau/nv50/nv50_vbo.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/gallium/drivers/nouveau/nv50/nv50_vbo.c b/src/gallium/drivers/nouveau/nv50/nv50_vbo.c index 8c73423ab49..b8ea652a727 100644 --- a/src/gallium/drivers/nouveau/nv50/nv50_vbo.c +++ b/src/gallium/drivers/nouveau/nv50/nv50_vbo.c @@ -752,8 +752,6 @@ nv50_draw_vbo_kick_notify(struct nouveau_pushbuf *chan) struct nv50_screen *screen = chan->user_priv; nouveau_fence_update(&screen->base, true); - - nv50_bufctx_fence(screen->cur_ctx->bufctx_3d, true); } void