From: Timo Lindfors <timo.lindfors@iki.fi>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Timo Lindfors <timo.lindfors@iki.fi>,
David Airlie <airlied@redhat.com>,
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>,
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 18:46:41 +0300 (EEST) [thread overview]
Message-ID: <alpine.DEB.2.20.2405071833510.21166@mail.home> (raw)
In-Reply-To: <obume4wdvgxc3zljnelhpwrg2rouae322nak5jy3s4hsruoddd@stoopms6fo2a>
On Tue, 7 May 2024, Gerd Hoffmann wrote:
> Worth trying: use vnc. The qemu vnc server will skip updates when the
> network pipeline is full. That throttles the frame rate, but also
> reduces the display update latency.
With Debian 12 it seems that the virtio + vnc + firefox combination
results in a black firefox window. Adding MOZ_ENABLE_WAYLAND=1 makes
the browser visible but I still see the constant redraw behavior when scrolling.
The qxl + spice + firefox combination scrolls smoothly even if I force
firefox to use wayland. I suppose I could write a more synthetic test if
it would be useful? With systemtap I can trace what happens during a single
scroll event.
> In general the trend seems to be to move to in-guest remote desktop
> solutions. Do NOT make VMs a special case with a special solution,
> instead handle VMs like bare metal. Commercial solutions exist for a
> while, some of them are doing hardware-assisted video encoding to send
> the display as video stream to the remote end. gnome+rdp is a new
> player here, clearly worth a try.
Yes this makes sense. I'm definitely not trying to stick to a particular
technology but instead try to find the best FOSS solution for the use case
of hosting linux desktops on a server.
-Timo
next prev parent reply other threads:[~2024-05-07 15:46 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 [this message]
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.2405071833510.21166@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 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®