qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 1/1] hw/display: Support per-head resolutions with virtio-gpu
Date: Wed, 27 Aug 2025 17:43:53 +0100	[thread overview]
Message-ID: <aK81yUqtwoZ9_29l@redhat.com> (raw)
In-Reply-To: <CAGZECHOL=v50aV0vcCHdFxb69TmH7mXry2NEhu+EZZnWztRO-A@mail.gmail.com>

On Wed, Aug 27, 2025 at 11:48:34AM -0400, Andrew Keesler wrote:
> Sending again (replying all this time).
> 
> > IIUC from the current code, xres/yres are only set against the
> > first head. The 2nd and later heads are left undefined by the
> > virtio-gpu-base code at least - I'm unclear if something else
> > in QEMU will fill in defaults later, or if they set to 0x0.
> 
> That is correct - xres/yres are only set against the first head in the
> current code. The wording in my commit message (and cover letter) was
> misleading. I will fix that to say that "If no
> virtio_gpu_base_conf.outputs are provided,
> virtio_gpu_base_conf.xres/virtio_gpu_base_conf.yres will still be
> respected _for the first head_ for backwards compatibility".
> 
> The only way I could get QEMU to fill in xres/yres for a 2nd and later
> head was to trigger virtio_gpu_ops.ui_info via a VNC client.
> 
> > Is it relevant to set xres/yres on outputs, even when they are
> > not (yet) enabled ?  Perhaps we should have an explicit 'enabled: bool'
> > property in the 'outputs' struct ?
> 
> Maybe you might want to set xres/yres on an output, but not enable it
> yet? I don't have any concrete examples of when you might want to do
> that, maybe you have some examples?

No, I don't have an example.

> I feel like I could see a user setting xres/yres on an output,
> forgetting to set enabled on that output, and then being confused why
> their head is blank. Because of this, my vote would be to default to
> enabling an output when it has configuration. I am easily swayed by
> your guidance, though.

Ok, lets just document that setting xres/yres will cause the
output to be automatically enabled. We can always retrofit
an 'enabled' property at a later date if someone arrives with
a use case for setting res without enabling the output.

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 :|



  reply	other threads:[~2025-08-27 16:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-22 19:08 [PATCH 0/1] Support per-head resolutions with virtio-gpu Andrew Keesler
2025-07-22 19:08 ` [PATCH 1/1] hw/display: " Andrew Keesler
2025-08-27 13:46   ` Daniel P. Berrangé
2025-08-27 15:48     ` Andrew Keesler
2025-08-27 16:43       ` Daniel P. Berrangé [this message]
2025-08-28 15:47         ` Andrew Keesler
2025-08-28 15: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=aK81yUqtwoZ9_29l@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 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).