From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH 8/9] vnc: add support for extended desktop resize
Date: Thu, 3 Dec 2020 11:28:45 +0000 [thread overview]
Message-ID: <20201203112845.GC2952498@redhat.com> (raw)
In-Reply-To: <20201203110806.13556-9-kraxel@redhat.com>
On Thu, Dec 03, 2020 at 12:08:04PM +0100, Gerd Hoffmann wrote:
> The extended desktop resize encoding adds support for (a) clients
> sending resize requests to the server, and (b) multihead support.
>
> This patch implements (a). All resize requests are rejected by qemu.
> Qemu can't resize the framebuffer on its own, this is in the hands of
> the guest, so all qemu can do is forward the request to the guest.
> Should the guest actually resize the framebuffer we can notify the vnc
> client later with a separate message.
>
> This requires support in the display device. Works with virtio-gpu.
>
> https://github.com/rfbproto/rfbproto/blob/master/rfbproto.rst#extendeddesktopsize-pseudo-encoding
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> ui/vnc.h | 2 ++
> ui/vnc.c | 64 +++++++++++++++++++++++++++++++++++++++++++++++++++++++-
> 2 files changed, 65 insertions(+), 1 deletion(-)
>
> diff --git a/ui/vnc.h b/ui/vnc.h
> index c8d3ad9ec496..77a310947bd6 100644
> --- a/ui/vnc.h
> +++ b/ui/vnc.h
> @@ -442,6 +442,7 @@ enum {
>
> enum VncFeatures {
> VNC_FEATURE_RESIZE,
> + VNC_FEATURE_RESIZE_EXT,
> VNC_FEATURE_HEXTILE,
> VNC_FEATURE_POINTER_TYPE_CHANGE,
> VNC_FEATURE_WMVI,
> @@ -456,6 +457,7 @@ enum VncFeatures {
> };
>
> #define VNC_FEATURE_RESIZE_MASK (1 << VNC_FEATURE_RESIZE)
> +#define VNC_FEATURE_RESIZE_EXT_MASK (1 << VNC_FEATURE_RESIZE_EXT)
> #define VNC_FEATURE_HEXTILE_MASK (1 << VNC_FEATURE_HEXTILE)
> #define VNC_FEATURE_POINTER_TYPE_CHANGE_MASK (1 << VNC_FEATURE_POINTER_TYPE_CHANGE)
> #define VNC_FEATURE_WMVI_MASK (1 << VNC_FEATURE_WMVI)
> diff --git a/ui/vnc.c b/ui/vnc.c
> index bdaf384f71a4..a15132faa96f 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -663,10 +663,35 @@ void vnc_framebuffer_update(VncState *vs, int x, int y, int w, int h,
> vnc_write_s32(vs, encoding);
> }
>
> +static void vnc_desktop_resize_ext(VncState *vs, bool reject)
> +{
> + vnc_lock_output(vs);
> + vnc_write_u8(vs, VNC_MSG_SERVER_FRAMEBUFFER_UPDATE);
> + vnc_write_u8(vs, 0);
> + vnc_write_u16(vs, 1); /* number of rects */
> + vnc_framebuffer_update(vs,
> + reject ? 1 : 0,
> + reject ? 3 : 0,
> + vs->client_width, vs->client_height,
> + VNC_ENCODING_DESKTOP_RESIZE_EXT);
> + vnc_write_u8(vs, 1); /* number of screens */
> + vnc_write_u8(vs, 0); /* padding */
> + vnc_write_u8(vs, 0); /* padding */
> + vnc_write_u8(vs, 0); /* padding */
> + vnc_write_u32(vs, 0); /* screen id */
> + vnc_write_u16(vs, 0); /* screen x-pos */
> + vnc_write_u16(vs, 0); /* screen y-pos */
> + vnc_write_u16(vs, vs->client_width);
> + vnc_write_u16(vs, vs->client_height);
> + vnc_write_u32(vs, 0); /* screen flags */
> + vnc_unlock_output(vs);
> + vnc_flush(vs);
> +}
>
> static void vnc_desktop_resize(VncState *vs, bool force)
> {
> - if (vs->ioc == NULL || !vnc_has_feature(vs, VNC_FEATURE_RESIZE)) {
> + if (vs->ioc == NULL || (!vnc_has_feature(vs, VNC_FEATURE_RESIZE) &&
> + !vnc_has_feature(vs, VNC_FEATURE_RESIZE_EXT))) {
> return;
> }
> if (vs->client_width == pixman_image_get_width(vs->vd->server) &&
> @@ -681,6 +706,12 @@ static void vnc_desktop_resize(VncState *vs, bool force)
> pixman_image_get_height(vs->vd->server) >= 0);
> vs->client_width = pixman_image_get_width(vs->vd->server);
> vs->client_height = pixman_image_get_height(vs->vd->server);
> +
> + if (vnc_has_feature(vs, VNC_FEATURE_RESIZE_EXT)) {
> + vnc_desktop_resize_ext(vs, false);
> + return;
> + }
> +
> vnc_lock_output(vs);
> vnc_write_u8(vs, VNC_MSG_SERVER_FRAMEBUFFER_UPDATE);
> vnc_write_u8(vs, 0);
> @@ -2110,6 +2141,9 @@ static void set_encodings(VncState *vs, int32_t *encodings, size_t n_encodings)
> case VNC_ENCODING_DESKTOPRESIZE:
> vs->features |= VNC_FEATURE_RESIZE_MASK;
> break;
> + case VNC_ENCODING_DESKTOP_RESIZE_EXT:
> + vs->features |= VNC_FEATURE_RESIZE_EXT_MASK;
IIUC, we shouldn't set this flag unless all current displays adapters
associated with the VNC server support the "ui_info" callbacks,
otherwise the client will think it can send resize requests
but they'll never be honoured.
> + break;
> case VNC_ENCODING_POINTER_TYPE_CHANGE:
> vs->features |= VNC_FEATURE_POINTER_TYPE_CHANGE_MASK;
> break;
> @@ -2431,6 +2465,34 @@ static int protocol_client_msg(VncState *vs, uint8_t *data, size_t len)
> break;
> }
> break;
> + case VNC_MSG_CLIENT_SET_DESKTOP_SIZE:
> + {
> + size_t size;
> + uint8_t screens;
> + uint16_t width;
> + uint16_t height;
> + QemuUIInfo info;
> +
> + if (len < 8) {
> + return 8;
> + }
> +
> + screens = read_u8(data, 6);
> + size = 8 + screens * 16;
> + if (len < size) {
> + return size;
> + }
> +
> + width = read_u16(data, 2);
> + height = read_u16(data, 4);
> + vnc_desktop_resize_ext(vs, true);
> +
> + memset(&info, 0, sizeof(info));
> + info.width = width;
> + info.height = height;
> + dpy_set_ui_info(vs->vd->dcl.con, &info);
> + break;
> + }
> default:
> VNC_DEBUG("Msg: %d\n", data[0]);
> vnc_client_error(vs);
> --
> 2.27.0
>
>
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2020-12-03 11:30 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 11:07 [PATCH 0/9] vnc: support some new extensions Gerd Hoffmann
2020-12-03 11:07 ` [PATCH 1/9] console: allow con==NULL in dpy_set_ui_info Gerd Hoffmann
2020-12-04 11:28 ` Marc-André Lureau
2020-12-03 11:07 ` [PATCH 2/9] console: add check for ui_info pointer Gerd Hoffmann
2020-12-04 11:32 ` Marc-André Lureau
2020-12-03 11:07 ` [PATCH 3/9] vnc: use enum for features Gerd Hoffmann
2020-12-04 11:32 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 4/9] vnc: drop unused copyrect feature Gerd Hoffmann
2020-12-04 11:32 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 5/9] vnc: add pseudo encodings Gerd Hoffmann
2020-12-04 11:34 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 6/9] vnc: add alpha cursor support Gerd Hoffmann
2020-12-04 11:39 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 7/9] vnc: force initial resize message Gerd Hoffmann
2020-12-04 11:57 ` Marc-André Lureau
2020-12-08 6:57 ` Gerd Hoffmann
2020-12-08 8:02 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 8/9] vnc: add support for extended desktop resize Gerd Hoffmann
2020-12-03 11:28 ` Daniel P. Berrangé [this message]
2020-12-04 6:37 ` Gerd Hoffmann
2020-12-04 12:25 ` Daniel P. Berrangé
2020-12-04 12:15 ` Daniel P. Berrangé
2020-12-04 12:24 ` Marc-André Lureau
2020-12-03 11:08 ` [PATCH 9/9] qxl: add ui_info callback Gerd Hoffmann
2020-12-04 12:20 ` Daniel P. Berrangé
2020-12-04 12:45 ` Marc-André Lureau
2020-12-04 12:50 ` Daniel P. Berrangé
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=20201203112845.GC2952498@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
/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;
as well as URLs for NNTP newsgroup(s).