From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Cc: Paul Brook <paul@codesourcery.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [Qemu-devel] [PATCH 0 of 7] [UPDATE] DisplayState interface change
Date: Thu, 27 Nov 2008 17:42:44 -0600 [thread overview]
Message-ID: <492F3074.6060200@codemonkey.ws> (raw)
In-Reply-To: <492D9EA4.9050008@eu.citrix.com>
Stefano Stabellini wrote:
> Paul Brook wrote:
>
>
>
>>> - do not use is_active_console, use is_graphic_console instead.
>>>
>> This is wrong. There may be multiple graphic consoles.
>>
>
> I thought we wanted to move to a model in which a DisplayState
> corresponds to a single QEMUConsole and a single graphic device.
> This is the reason for Anthony to ask me this update, if I am not mistaken.
>
I need to look more closely at the patches (and I will tomorrow), but to
me, the use of is_active_console or is_graphics_console is a red
herring. Nothing should never need to know whether it's the "active"
console. Such a concept simply shouldn't exist.
I think this is Paul's point about multiple graphics consoles. If you
have two graphics consoles, than the concept of active console doesn't
make very much sense. Is that what you were thinking Paul?
>>> This patch changes the graphical_console_init function to return an
>>> allocated DisplayState instead of a QEMUConsole.
>>>
>> You should also remove QEMUConsole.
>>
>
> I removed QEMUConsole from the graphic devices, I am not going to
> completely get rid of it because it is currently needed by text consoles
> and to multiplex multiple consoles.
>
QEMUConsole is just a typedef right now. Could you remove the typedef?
It should become unused after your patch.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2008-11-27 23:42 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 17:47 [Qemu-devel] [PATCH 0 of 7] [UPDATE] DisplayState interface change Stefano Stabellini
2008-11-26 18:40 ` Paul Brook
2008-11-26 19:08 ` Stefano Stabellini
2008-11-27 23:42 ` Anthony Liguori [this message]
2008-11-28 0:29 ` Paul Brook
2008-12-02 19:35 ` Anthony Liguori
2008-12-11 11:55 ` Stefano Stabellini
2008-12-11 12:39 ` Paul Brook
2008-12-11 15:22 ` Stefano Stabellini
2008-12-11 15:29 ` Paul Brook
2008-12-11 15:37 ` Stefano Stabellini
2008-12-11 15:45 ` Paul Brook
2008-11-28 11:03 ` Stefano Stabellini
2008-12-02 19:33 ` 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=492F3074.6060200@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).