qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: "Hervé Poussineau" <hpoussin@reactos.org>
Cc: qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 4/4] [RfC] stdvga: add xres and yres properties.
Date: Mon, 13 Mar 2017 16:17:55 +0100	[thread overview]
Message-ID: <1489418275.13264.39.camel@redhat.com> (raw)
In-Reply-To: <94414912-f18a-bb2b-4055-126261181e89@reactos.org>

On Do, 2017-03-09 at 22:03 +0100, Hervé Poussineau wrote:
> Le 09/03/2017 à 09:38, Gerd Hoffmann a écrit :
> > Add two new registers to the qemu extended register range, carrying the
> > suggested width and height of the display device.  In case the xres and
> > yres properties are set, fill these new registers accordingly.
> >
> > Additionally guest driver updates are needed to support the new
> > registers.  These changes will probably land in linux kernel 4.12.
> 
> Is it possible to provide a mecanism to tell guest that the preferred
> default size changed?
> For example, the user can resize the VM window on host, and guest will
> auto-adapt to new size/resolution.
> It is already working like this on VirtualBox with VM Additions.

Well, sure, we can pimp the virtual hardware even more.  Adding such a
notification is pretty invasive though.  We'll have to add irq support
to stdvga, on both guest and host.

So the question is:  Is it worth the effort?  How far we want take it
and why?

For linux this would require a pretty recent guest kernel with the (to
be written) driver changes added.  If you have a recent guest kernel
anyway you can just switch to virtio-gpu where this works today (gtk ui,
or spice with guest agent active).  So I see little reason to put too
much effort into stdvga, for linux guests.

For non-linux guests (where no virtio-gpu driver is available) better
stdvga support might be more useful.  Do you have specific guests in
mind?  Looking at your email address I suspect that is the case ...

While being at it:  We might also consider adding hardware cursor
support.  Seems that is standard these days.  Wayland has no software
cursor support any more, therefore you have no mouse pointer when
running wayland on stdvga (again: on virtio-gpu it'll work just fine).

cheers,
  Gerd

      reply	other threads:[~2017-03-13 15:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-09  8:38 [Qemu-devel] [PATCH v2 0/4] vga: make display size configurable Gerd Hoffmann
2017-03-09  8:38 ` [Qemu-devel] [PATCH v2 1/4] virtio-gpu: add xres and yres properties Gerd Hoffmann
2017-03-09  8:38 ` [Qemu-devel] [PATCH v2 2/4] qxl: " Gerd Hoffmann
2017-03-09  8:38 ` [Qemu-devel] [PATCH v2 3/4] stdvga: move common properties to common base class Gerd Hoffmann
2017-03-09  8:38 ` [Qemu-devel] [PATCH v2 4/4] [RfC] stdvga: add xres and yres properties Gerd Hoffmann
2017-03-09 21:03   ` Hervé Poussineau
2017-03-13 15:17     ` Gerd Hoffmann [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=1489418275.13264.39.camel@redhat.com \
    --to=kraxel@redhat.com \
    --cc=hpoussin@reactos.org \
    --cc=mst@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).