From: Timo Lindfors <timo.lindfors@iki.fi>
To: David Airlie <airlied@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Maxime Ripard <mripard@kernel.org>,
Steven Rostedt <rostedt@goodmis.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: Tue, 7 May 2024 09:38:56 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.20.2405070933070.20162@mail.home> (raw)
In-Reply-To: <CAMwc25qMXOFOfKsa7BRi3dz125PDyvVtgTty0Q4bkAFftJDLqQ@mail.gmail.com>
On Tue, 7 May 2024, David Airlie 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 would love to switch to virtio. It works ok for local virtual machines
but I have many users who are using Linux desktops hosted on a powerful
server where it is more difficult. With spice and qxl scrolling in a web
browser is smooth, with spice and virtio it seems like larger parts are
getting fully redrawn (and resent over network?). Now that new gnome is
going to come with RDP support I'm also considering switching to that. Any
tips would be appreciated.
Here's a quick (1min42s) demo video that I recorded. spice+qxl on the
left, spice+virtio on the right. The VMs were created from the exact same
disk image template.
https://lindi.iki.fi/lindi/qxl/spice_qxl_vs_virtio.webm
-Timo
next prev parent reply other threads:[~2024-05-07 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-02 12:16 [BUG][v6.9-rc6] Deadlock with: Revert "drm/qxl: simplify qxl_fence_wait" 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 [this message]
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
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=alpine.DEB.2.20.2405070933070.20162@mail.home \
--to=timo.lindfors@iki.fi \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.