From: Anders Blomdell <anders.blomdell@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>, David Airlie <airlied@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Maxime Ripard <mripard@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Alex Constantino <dreaming.about.electric.sheep@gmail.com>,
Timo Lindfors <timo.lindfors@iki.fi>,
Gerd Hoffmann <kraxel@redhat.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>
Subject: Re: [BUG][v6.9-rc6] Deadlock with: Revert "drm/qxl: simplify qxl_fence_wait"
Date: Wed, 8 May 2024 14:42:38 +0200 [thread overview]
Message-ID: <e26ba70d-340a-43bf-8e39-7214e76ab141@gmail.com> (raw)
In-Reply-To: <20240507050354.66bd88a0@rorschach.local.home>
On 2024-05-07 11:03, Steven Rostedt wrote:
> On Tue, 7 May 2024 15:54:21 +1000
> David Airlie <airlied@redhat.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?
It deadlocks on 6.8.8 under qemu/kvm, reverting the patch fixes the problem there as well (6.8.7 hangs as well, but I have not tested reverting on that version)
/Anders
prev parent reply other threads:[~2024-05-08 12:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:16 Steven Rostedt
2024-05-02 12:30 ` Steven Rostedt
2024-05-04 8:39 ` Steven Rostedt
2024-05-06 12:45 ` Maxime Ripard
2024-05-06 20:28 ` Linus Torvalds
2024-05-07 5:54 ` David Airlie
2024-05-07 6:38 ` Timo Lindfors
2024-05-07 10:21 ` Gerd Hoffmann
2024-05-07 15:46 ` Timo Lindfors
2024-05-08 9:56 ` Gerd Hoffmann
2024-05-07 9:03 ` Steven Rostedt
2024-05-08 12:42 ` Anders Blomdell [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e26ba70d-340a-43bf-8e39-7214e76ab141@gmail.com \
--to=anders.blomdell@gmail.com \
--cc=airlied@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dreaming.about.electric.sheep@gmail.com \
--cc=kraxel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rostedt@goodmis.org \
--cc=timo.lindfors@iki.fi \
--cc=torvalds@linux-foundation.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®