From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 4 of 5] [UPDATE] DisplayState interface change
Date: Tue, 25 Nov 2008 12:23:14 +0000 [thread overview]
Message-ID: <492BEE32.6020209@eu.citrix.com> (raw)
In-Reply-To: <492B0781.6050505@codemonkey.ws>
Anthony Liguori wrote:
> I'm not asking you to do that refactoring. But since we all pretty much
> agree that this is how things should look, I want to make sure that the
> DisplayState API takes all of this into account.
>
> So in that vein, I'd like to see all the things that call
> graphic_console_init changed to not take a DisplayState, but rather to
> have graphic_console_init() return an allocated DisplayState. These
> functions should then return a DisplayState which can be passed to VNC/SDL.
>
> From what I can tell, this is not a huge change. You shouldn't have to
> really touch any of the console code. I think this is important to sure
> up what the DisplayState API looks like and how the rest of QEMU
> interacts with it.
>
> If this seems like a major refactoring, let me know and either you're
> misunderstanding what I'm suggesting or I've miscalculated how much
> change is required here :-)
That's fine, it is a simple change, it was me that didn't understand
correctly what you were suggesting.
Since at the moment we don't have a DisplayState multiplexing function,
this means that we are going to keep the text_console_init as it is now
so that we can still the serial and the monitor interfaces, right?
next prev parent reply other threads:[~2008-11-25 12:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 17:08 [Qemu-devel] [PATCH 4 of 5] [UPDATE] DisplayState interface change Stefano Stabellini
[not found] ` <200811211736.23473.paul@codesourcery.com>
2008-11-21 17:45 ` Stefano Stabellini
2008-11-22 20:00 ` Anthony Liguori
2008-11-24 16:51 ` Stefano Stabellini
2008-11-24 19:58 ` Anthony Liguori
2008-11-25 12:23 ` Stefano Stabellini [this message]
2008-11-25 12:38 ` Stefano Stabellini
2008-11-25 14:35 ` 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=492BEE32.6020209@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.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).