From: Gerd Hoffmann <kraxel@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: Dave Airlie <airlied@redhat.com>,
qemu-devel@nongnu.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/9] virtio-gpu/2d: add virtio gpu core code
Date: Tue, 17 Mar 2015 09:21:46 +0100 [thread overview]
Message-ID: <1426580506.27188.46.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <550739CE.90903@redhat.com>
Hi,
> > + for (i = 0; i < g->conf.max_outputs; i++) {
> > + g->scanout[i].con =
> > + graphic_console_init(DEVICE(g), i, &virtio_gpu_ops, g);
> > + if (i > 0) {
> > + dpy_gfx_replace_surface(g->scanout[i].con, NULL);
>
> GTK can't cope very well with NULL surfaces (read: after patch 7 (when
> using -vga virtio finally works) "x86_64-softmmu/qemu-system-x86_64 -vga
> virtio -display gtk" segfaults). With SDL (SDL2), it works fine.
Yes, I know. I have a gtk patch for that in the pipeline.
But that alone doesn't get multihead work sanely as there is at least
one more problem to tackle: Mouse coordinates are not correct. Our
options are:
(a) Have guest notify host about screen arrangement, then transform
coordinates in qemu. Dave did that initially.
(b) Have a guest agent (spice style).
(c) Have one tablet per head and link them. That is very simliar to
physical hardware (think touchscreen).
I think (c) will work best long-term, but it is also the most difficult
one as various projects are involved here to get the guest-side
configuration done.
I've changed the number of heads to be 1 by default, we better sort all
those issues before we flip the multihead default switch.
cheers,
Gerd
next prev parent reply other threads:[~2015-03-17 8:21 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-13 9:47 [Qemu-devel] [PATCH 0/9] add virtio-gpu with 2d support Gerd Hoffmann
2015-03-13 9:47 ` [Qemu-devel] [PATCH] opengl: require glx Gerd Hoffmann
2015-03-13 10:31 ` Gerd Hoffmann
2015-03-13 9:47 ` [Qemu-devel] [PATCH 1/9] virtio-gpu/2d: add hardware spec include file Gerd Hoffmann
2015-03-16 16:20 ` Max Reitz
2015-03-17 7:54 ` Gerd Hoffmann
2015-03-13 9:47 ` [Qemu-devel] [PATCH 2/9] virtio-gpu/2d: add virtio gpu core code Gerd Hoffmann
2015-03-16 18:28 ` Max Reitz
2015-03-16 20:15 ` Max Reitz
2015-03-17 8:21 ` Gerd Hoffmann [this message]
2015-03-13 9:47 ` [Qemu-devel] [PATCH 3/9] virtio-gpu-pci: add virtio pci support Gerd Hoffmann
2015-03-16 18:49 ` Max Reitz
2015-03-13 9:47 ` [Qemu-devel] [PATCH 4/9] virtio-vga: add virtio gpu device with vga compatibility Gerd Hoffmann
2015-03-16 19:17 ` Max Reitz
2015-03-13 9:47 ` [Qemu-devel] [PATCH 5/9] virtio-vga: add '-vga virtio' support Gerd Hoffmann
2015-03-16 19:30 ` Max Reitz
2015-03-13 9:47 ` [Qemu-devel] [PATCH 6/9] virtio-vga: add vgabios configuration Gerd Hoffmann
2015-03-16 19:38 ` Max Reitz
2015-03-13 9:47 ` [Qemu-devel] [PATCH 7/9] virtio-vga: add vgabios binary Gerd Hoffmann
2015-03-16 19:39 ` Max Reitz
2015-03-13 9:47 ` [Qemu-devel] [PATCH 8/9] virtio-gpu: add to display-vga test Gerd Hoffmann
2015-03-16 17:16 ` Paolo Bonzini
2015-03-17 8:25 ` Gerd Hoffmann
2015-03-13 9:47 ` [Qemu-devel] [PATCH 9/9] [hack] virtio-gpu: maskerade as -device VGA Gerd Hoffmann
2015-03-23 20:19 ` [Qemu-devel] [PATCH 0/9] add virtio-gpu with 2d support Christopher Covington
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=1426580506.27188.46.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@redhat.com \
--cc=mreitz@redhat.com \
--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).