From: Anthony Liguori <anthony@codemonkey.ws>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change
Date: Thu, 20 Nov 2008 17:07:08 -0600 [thread overview]
Message-ID: <4925ED9C.90703@codemonkey.ws> (raw)
In-Reply-To: <200811202246.18906.paul@codesourcery.com>
Paul Brook wrote:
>> There are really two parts to this patch. One part is a completely
>> mechanical conversion of things like ds->linesize to
>> ds->surface->linesize. The second is the guys of the API change.
>>
>> If you introduce accessors to access things like linesize from
>> DisplayState, so something like:
>>
>> int ds_get_linesize(DisplayState *ds) {
>> return ds->linesize;
>> }
>>
>
> I think this sort of thing should be going via the console structures.
> i.e. vga emulation deals entirely with a QEMUConsole. sdl/vnc deal entirely
> with a DisplayState, and qemu mediates in between.
>
I'm not sure. You can't really hide the fact that there are two VGA
cards to the SDL/VNC backend. I think a model where each emulated VGA
device had a DisplayState, and each DisplayState had an SDL/VNC backend
connected to it could work.
That way, you could have two VNC servers for each of the two VGA
devices. SDL is unworkable for multiple monitors AFAIK so it's kind of
a moot point.
Where you thinking that we would try to have a QEMUConsole with each VGA
card and then multiplex the QEMUConsoles on a single DisplayState?
Couldn't we do the same by multiplexing two DisplayState's onto one
DisplayState?
I don't think required interface for QEMUConsole would be much different
than DisplayState so it's unclear to me if two structures are really needed.
Anyway, Stefano, please add accessors in some form to help with review
of this patch. If we decide we need a QEMUConsole abstraction, it's
easy enough to update the patch to modify some of the accessors.
Regards,
Anthony Liguori
> Paul
>
next prev parent reply other threads:[~2008-11-20 23:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-20 16:58 [Qemu-devel] [PATCH 1 of 2] [UPDATE] DisplayState interface change Stefano Stabellini
[not found] ` <200811201737.00254.paul@codesourcery.com>
2008-11-20 17:48 ` Stefano Stabellini
[not found] ` <200811201823.22742.paul@codesourcery.com>
2008-11-20 18:36 ` Stefano Stabellini
[not found] ` <200811201839.24213.paul@codesourcery.com>
2008-11-20 19:02 ` Stefano Stabellini
[not found] ` <200811211040.44235.paul@codesourcery.com>
2008-11-21 11:31 ` Stefano Stabellini
2008-11-20 18:58 ` Anthony Liguori
[not found] ` <200811202246.18906.paul@codesourcery.com>
2008-11-20 23:06 ` Anthony Liguori
2008-11-20 23:07 ` Anthony Liguori [this message]
2008-11-20 23:16 ` Anthony Liguori
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=4925ED9C.90703@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).