From fcd1c4b9e748c7d5a0391f9808f2d13bffca7b52 Mon Sep 17 00:00:00 2001 From: Mel Henning Date: Tue, 7 Oct 2025 18:40:32 -0400 Subject: [PATCH] nvk: FLUSH_PENDING_WRITES in gr semaphore release The proprietary driver seems to always do this before a graphics semaphore release. This is presumably weaker than a WFI because it's never emitted for pipeline barriers. Reviewed-by: Mary Guillemard Part-of: --- src/nouveau/vulkan/nvk_event.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/nouveau/vulkan/nvk_event.c b/src/nouveau/vulkan/nvk_event.c index d6ad820ebb3..7e43bbdee3f 100644 --- a/src/nouveau/vulkan/nvk_event.c +++ b/src/nouveau/vulkan/nvk_event.c @@ -164,7 +164,8 @@ nvk_event_report_semaphore(struct nvk_cmd_buffer *cmd, { uint8_t subc = nvk_cmd_buffer_last_subchannel(cmd); if (subc == SUBC_NV9097) { - struct nv_push *p = nvk_cmd_buffer_push(cmd, 5); + struct nv_push *p = nvk_cmd_buffer_push(cmd, 7); + P_IMMD(p, NV9097, FLUSH_PENDING_WRITES, 0); P_MTHD(p, NV9097, SET_REPORT_SEMAPHORE_A); P_NV9097_SET_REPORT_SEMAPHORE_A(p, addr >> 32); P_NV9097_SET_REPORT_SEMAPHORE_B(p, addr);