[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240507050354.66bd88a0@rorschach.local.home>
Date: Tue, 7 May 2024 05:03:54 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: David Airlie <airlied@...hat.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>, Maxime Ripard
<mripard@...nel.org>, LKML <linux-kernel@...r.kernel.org>, Alex Constantino
<dreaming.about.electric.sheep@...il.com>, Timo Lindfors
<timo.lindfors@....fi>, Gerd Hoffmann <kraxel@...hat.com>, Maarten
Lankhorst <maarten.lankhorst@...ux.intel.com>, Thomas Zimmermann
<tzimmermann@...e.de>, Daniel Vetter <daniel@...ll.ch>
Subject: Re: [BUG][v6.9-rc6] Deadlock with: Revert "drm/qxl: simplify
qxl_fence_wait"
On Tue, 7 May 2024 15:54:21 +1000
David Airlie <airlied@...hat.com> wrote:
> I expec this will reintroduce the other problems that caused this
> change in the first place, but I think this should at least bring us
> back to regression equilibrium. I can't recommend anyone use qxl hw
> over virtio-gpu hw in their VMs, since virtio-gpu is actually hw
> designed for virt.
I agree that it will likely cause the issues that this was addressing
to come back, but you can't have a fix that introduces a deadlock.
Perhaps the deadlock didn't exist before, and the printk updates
changed the way it works to introduce it now?
-- Steve
Powered by blists - more mailing lists