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: Thu, 28 Aug 2025 16:50:08 +0100	[thread overview]
Message-ID: <aLB6sC6qI1RN_dr4@redhat.com> (raw)
In-Reply-To: <CAGZECHNkRo=Oejh9CgAAV+Qa8f_PgdhvyOy+rAGNRG29Datt1Q@mail.gmail.com>

On Thu, Aug 28, 2025 at 11:47:23AM -0400, Andrew Keesler wrote:
> > > I think we should probably report an error if xres / yres
> > > are set at the global level and also set against any individual
> > > output, so the two approaches are mutually exclusive.
> 
> > ACK - fixed for the next patch.
> 
> Doh, I ran into an error. Seems like if I don't set xres/yres, then it
> gets defaulted to 1280x800.
> 
> 
> https://gitlab.com/qemu-project/qemu/-/blob/master/include/hw/virtio/virtio-gpu.h#L175-176
> 
> So...could we just get away with documenting that if you set xres/yres
> and outputs[0].xres/yres, then the later is going to overwrite the
> former? I'm not sure how to detect if xres/yres has been set globally
> to 1280x800, or if we are just getting the defaults.
> 
> What do you think?

Oh it probably isn't worth the hassle for a mere error report. Instead
just document that per-output takes priority if both are set.


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-28 17:25 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é
2025-08-28 15:47         ` Andrew Keesler
2025-08-28 15:50           ` 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=aLB6sC6qI1RN_dr4@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).