qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: John Baboval <baboval@spineless.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Multi-head support RFC
Date: Thu, 07 Nov 2013 10:54:58 -0500	[thread overview]
Message-ID: <527BB7D2.6070503@spineless.org> (raw)
In-Reply-To: <1383831984.3511.78.camel@nilsson.home.kraxel.org>

On 11/7/2013 8:46 AM, Gerd Hoffmann wrote:
>    Hi,
>
>> As far as the EDID is concerned, there can only be one EDID for a
>> display+hw pair, or the guest won't know what to do. In my use-case, I
>> simply pass real EDIDs through, and create a full-screen window for each
>> real monitor.
> Ok, makes sense.
>
>> If you wanted to have two UIs displaying the same
>> DisplaySurface, the EDID would have to come from one of them, and the
>> other would have to clip, or scale.
> Yes.
>
>>> Why not?  That is exactly my plan.  Just have the virtual graphic card
>>> call graphic_console_init() multiple times, once for each display
>>> connector it has.
>>>
>>> Do you see fundamental issues with that approach?
>> Currently only one QemuConsole is active at a time, so that would have
>> to change....
> That isn't mandatory any more.  It is still the default behavior of a
> DisplayChangeListener to follow the active_console, for compatibility
> reasons.  SDL and VNC still behave that way.
>
> You can explicitly bind a DisplayChangeListener to a QemuConsole though,
> by setting DisplayChangeListener->con before calling
> register_displaychangelistener().
>
> gtk binds to QemuConsole #0.
>
> spice creates a display channel per (graphical) console.  Each display
> channel has a DisplayChangeListener instance, and each
> DisplayChangeListener is linked to a different QemuConsole.
>
> For your UI you probably want follow the spice model.  Have a
> DisplayChangeListener for each physical monitor of the host, have a
> fixed QemuConsole bound to each DisplayChangeListener.
> DisplayChangeListeners can come and go at runtime just fine, so you
> should be able to create/destroy them on monitor plug/unplug events on
> the host.

I think the best thing for me to do at this point is to just start 
implementing with multiple QemuConsole, then, and post again when I have 
a better idea of what it ends up looking like. I'll keep you posted.

>
> cheers,
>    Gerd
>
>

  reply	other threads:[~2013-11-07 15:55 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
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 [this message]
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=527BB7D2.6070503@spineless.org \
    --to=baboval@spineless.org \
    --cc=kraxel@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).