[PATCH v2 1/1] Revert "drm/qxl: simplify qxl_fence_wait"

2024-04-04 Thread Alex Constantino
greport.cgi?bug=1054514 Signed-off-by: Alex Constantino --- drivers/gpu/drm/qxl/qxl_release.c | 50 +++ include/linux/dma-fence.h | 7 + 2 files changed, 52 insertions(+), 5 deletions(-) diff --git a/drivers/gpu/drm/qxl/qxl_release.c b/drivers/g

[PATCH v2 0/1] Revert "drm/qxl: simplify qxl_fence_wait"

2024-04-04 Thread Alex Constantino
80421] ret_from_fork_asm+0x1a/0x30 [ 20.780435] [ 20.780437] ---[ end trace ]--- ``` TLDR: this patch fixes the instability issues. But there may be warnings in dmesg. Errors in dmesg were observed too but they are unrelated to this patch. Thank you for your time. ---

[PATCH 1/1] drm/qxl: fixes qxl_fence_wait

2024-03-07 Thread Alex Constantino
m/qxl: simplify qxl_fence_wait") Link: https://lore.kernel.org/regressions/fb0fda6a-3750-4e1b-893f-97a3e402b...@leemhuis.info Reported-by: Timo Lindfors Closes: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1054514 Signed-off-by: Alex Constantino --- drivers/gpu/drm/qx

[PATCH 0/1] drm/qxl: fixes qxl_fence_wait

2024-03-07 Thread Alex Constantino
xit 0 ``` >From what I could find online it seems that users that have been affected by this problem just tend to move from QXL to VirtIO, that is why this bug has been hidding for over 3 years now. This issue was initially reported by Timo 4 months ago but the discussion seems to have stalled.