From: Gerd Hoffmann <kraxel@redhat.com>
To: Dave Airlie <airlied@gmail.com>
Cc: John Baboval <baboval@spineless.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] console muti-head some more design input
Date: Wed, 27 Nov 2013 08:11:10 +0100 [thread overview]
Message-ID: <1385536270.13867.25.camel@nilsson.home.kraxel.org> (raw)
In-Reply-To: <CAPM=9tyZ_0VAdZcNzfZAwqkBJ9o4ykc=m66t1sTvWuY8R6ijsg@mail.gmail.com>
Hi,
> So I think we probably do need treat multi-head windows as separate
> input devices, and/or have
> an agent in the guest to do the right thing by configuring multiple
> input devices to map to multiple outputs.
>
> I suppose spice must do something like this already, maybe they can
> tell me more.
Spice does it with a guest agent, which basically passes in the display
channel id as extra parameter (for the multihead-with-multiple-qxl cards
case).
Not fully sure how this works with a single qxl card and
scanout-rectangle-per-head, I suspect the pointer location is just
relative to the common surface backing all heads then.
cheers,
Gerd
next prev parent reply other threads:[~2013-11-27 7:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 6:24 [Qemu-devel] console muti-head some more design input Dave Airlie
2013-11-19 8:11 ` Gerd Hoffmann
2013-11-20 2:59 ` Dave Airlie
2013-11-20 4:06 ` John Baboval
2013-11-20 5:17 ` Dave Airlie
2013-11-20 5:18 ` Dave Airlie
2013-11-20 8:12 ` Gerd Hoffmann
2013-11-20 14:32 ` John Baboval
2013-11-20 15:14 ` Gerd Hoffmann
2013-11-20 15:49 ` John Baboval
2013-11-22 8:36 ` Gerd Hoffmann
2013-11-21 0:45 ` Dave Airlie
2013-11-22 8:41 ` Gerd Hoffmann
2013-11-27 4:29 ` Dave Airlie
2013-11-27 7:11 ` Gerd Hoffmann [this message]
2013-11-27 14:23 ` John Baboval
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=1385536270.13867.25.camel@nilsson.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=airlied@gmail.com \
--cc=baboval@spineless.org \
--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).