From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Andrew Keesler <ankeesler@google.com>
Cc: marcandre.lureau@gmail.com, qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/1] Support per-head resolutions with virtio-gpu
Date: Fri, 29 Aug 2025 09:18:40 +0100 [thread overview]
Message-ID: <aLFiYBMSZ95b0VLo@redhat.com> (raw)
In-Reply-To: <20250828175259.3831672-2-ankeesler@google.com>
On Thu, Aug 28, 2025 at 05:52:59PM +0000, Andrew Keesler wrote:
> In 454f4b0f, we started down the path of supporting separate
> configurations per display head (e.g., you have 2 heads - one with
> EDID name "AAA" and the other with EDID name "BBB").
>
> In this change, we add resolution to this configuration surface (e.g.,
> you have 2 heads - one with resolution 111x222 and the other with
> resolution 333x444).
>
> -display vnc=localhost:0,id=aaa,display=vga,head=0 \
> -display vnc=localhost:1,id=bbb,display=vga,head=1 \
> -device '{"driver":"virtio-vga",
> "max_outputs":2,
> "id":"vga",
> "outputs":[
> {
> "name":"AAA",
> "xres":111,
> "yres":222
> },
> {
> "name":"BBB",
> "xres":333,
> "yres":444
> }
> ]}'
>
> Here is the behavior matrix of the current resolution configuration
> surface (xres/yres) with the new resolution configuration surface
> (outputs[i].xres/yres).
>
> Case: !(xres || yres) && !(outputs[i].xres || outputs[i].yres)
> Behavior: current behavior - outputs[0] enabled with default xres/yres
>
> Case: (xres || yres) && !(outputs[i].xres || outputs[i].yres)
> Behavior: current behavior - outputs[0] enabled with xres/yres
>
> Case: !(xres || yres) && (outputs[i].xres || outputs[i].yres)
> Behavior: new behavior - outputs[i] enabled with outputs[i].xres/yres
>
> Case: (xres || yres) && (outputs[i].xres || outputs[i].yres)
> Behavior: new behavior - outputs[i] enabled with outputs[i].xres/yres
> ---
> hw/display/virtio-gpu-base.c | 10 ++++++++++
> include/hw/virtio/virtio-gpu.h | 2 ++
> qapi/virtio.json | 6 +++++-
> 3 files changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/hw/display/virtio-gpu-base.c b/hw/display/virtio-gpu-base.c
> index 7269477a1c..8bcbe5e837 100644
> --- a/hw/display/virtio-gpu-base.c
> +++ b/hw/display/virtio-gpu-base.c
> @@ -233,6 +233,16 @@ virtio_gpu_base_device_realize(DeviceState *qdev,
> g->req_state[0].width = g->conf.xres;
> g->req_state[0].height = g->conf.yres;
>
> + for (output_idx = 0, node = g->conf.outputs;
> + node && output_idx < g->conf.max_outputs;
> + output_idx++, node = node->next) {
> + if (node->value->xres || node->value->yres) {
This should be
if (node->value->has_xres && node->value->has_yres) {
> + g->enabled_output_bitmask |= (1 << output_idx);
> + g->req_state[output_idx].width = node->value->xres;
> + g->req_state[output_idx].height = node->value->yres;
> + }
> + }
> +
> g->hw_ops = &virtio_gpu_ops;
> for (i = 0; i < g->conf.max_outputs; i++) {
> g->scanout[i].con =
> diff --git a/include/hw/virtio/virtio-gpu.h b/include/hw/virtio/virtio-gpu.h
> index 9f16f89a36..7597e87971 100644
> --- a/include/hw/virtio/virtio-gpu.h
> +++ b/include/hw/virtio/virtio-gpu.h
> @@ -129,6 +129,8 @@ struct virtio_gpu_base_conf {
> uint32_t xres;
> uint32_t yres;
> uint64_t hostmem;
> + // If set, outputs[i].xres/yres takes precedent over xres/yres and enables
> + // the ith output.
I mean for that doc to be in the virtio.json file, so it gets into
the public QMP API documentation
> VirtIOGPUOutputList *outputs;
> };
>
> diff --git a/qapi/virtio.json b/qapi/virtio.json
> index 9d652fe4a8..9f753543cb 100644
> --- a/qapi/virtio.json
> +++ b/qapi/virtio.json
> @@ -970,11 +970,15 @@
> #
> # @name: the name of the output
> #
> +# @xres: horizontal resolution of the output in pixels (since 10.2)
> +#
> +# @yres: vertical resolution of the output in pixels (since 10.2)
> +#
> # Since: 10.1
> ##
>
> { 'struct': 'VirtIOGPUOutput',
> - 'data': { 'name': 'str' } }
> + 'data': { 'name': 'str', '*xres': 'uint16', '*yres': 'uint16' } }
>
> ##
> # @DummyVirtioForceArrays:
> --
> 2.51.0.338.gd7d06c2dae-goog
>
With 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 :|
prev parent reply other threads:[~2025-08-30 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-28 17:52 [PATCH v2 0/1] Support per-head resolutions with virtio-gpu Andrew Keesler
2025-08-28 17:52 ` [PATCH v2 1/1] " Andrew Keesler
2025-08-29 8:18 ` Daniel P. Berrangé [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=aLFiYBMSZ95b0VLo@redhat.com \
--to=berrange@redhat.com \
--cc=ankeesler@google.com \
--cc=marcandre.lureau@gmail.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 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.