From: John Baboval <baboval@spineless.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multi-head support RFC
Date: Fri, 08 Nov 2013 10:20:48 -0500 [thread overview]
Message-ID: <527D0150.1080805@spineless.org> (raw)
In-Reply-To: <CAPM=9twkuyzW7Ft1cSAqG35BpZMAeX_MiNS1Mr4FrO9t+zWgZg@mail.gmail.com>
On 11/06/2013 06:44 PM, Dave Airlie wrote:
> On Wed, Nov 6, 2013 at 8:57 PM, Gerd Hoffmann <kraxel@redhat.com> wrote:
>> Hi,
>>
>>> It currently just adds multiple DisplaySurfaces to the QemuConsole,
>>> now Gerd said he thought I should be using multiple QemuConsoles but I
>>> really didn't think this was a good idea,
>> Why?
> It's a fair question and I haven't tried the other way yet and I fully
> intend to do further investigating,
>
> I think my main reason was the current console at least when
> interacting with gtk frontend are done on a console per tab, now if we
> have multiple outputs I would want them to be visible at the same
> time, now I understand we could fix this but we'd need some sort of
> console grouping to say this group of consoles represent this set of
> outputs,
>
> Though further to that I'm not sure how we'd want to represent
> multiple graphic cards I assume we'd want to be able to see them all
> at once, but still have some sort of binding between separate outputs
> on one card.
Multiple graphic cards is actually a reasonable argument for the
multiple QemuConsole route, since each would have its own GraphicHwOps,
so it would simply be a matter of having the UI give the user a
mechanism for choosing which card to attach a new display to.
>
> Dave.
>
>
next prev parent reply other threads:[~2013-11-08 15:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 20:42 [Qemu-devel] Multi-head support RFC John Baboval
2013-11-06 1:46 ` Dave Airlie
2013-11-06 10:57 ` Gerd Hoffmann
2013-11-06 23:44 ` Dave Airlie
2013-11-07 13:00 ` Gerd Hoffmann
2013-11-08 15:20 ` John Baboval [this message]
2013-11-06 15:48 ` John Baboval
2013-11-06 10:55 ` Gerd Hoffmann
2013-11-06 15:39 ` John Baboval
2013-11-07 13:46 ` Gerd Hoffmann
2013-11-07 15:54 ` John Baboval
2013-11-15 20:14 ` John Baboval
2013-11-19 6:57 ` Gerd Hoffmann
2013-11-19 14:17 ` John Baboval
2013-11-20 7:39 ` Gerd Hoffmann
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=527D0150.1080805@spineless.org \
--to=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).