From: "Andreas Färber" <afaerber@suse.de>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Anthony Liguori <aliguori@us.ibm.com>,
"Todd T. Fries" <todd@fries.net>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] display: stop using DT_NOGRAPHIC, use DT_NONE
Date: Fri, 28 Jun 2013 13:45:30 +0200 [thread overview]
Message-ID: <51CD775A.3070006@suse.de> (raw)
In-Reply-To: <51CD73A4.2050107@msgid.tls.msk.ru>
Am 28.06.2013 13:29, schrieb Michael Tokarev:
> 28.06.2013 15:24, Peter Maydell wrote:
>> On 19 June 2013 13:34, Michael Tokarev <mjt@tls.msk.ru> wrote:
>>> It looks like initially there was -nographic option to turn
>>> off display, now there's another option of the same sort,
>>> -display none. But code in other places of qemu checks for
>>> DT_NOGRAPHIC and does not work well with -display none.
>>> Make DT_NOGRAPHIC an internal version which selects DT_NONE,
>>> and check for that in all other places where previously we
>>> checked for DT_NOGRAPHIC.
>>>
>>> While at it, rename two private variants of display (DT_DEFAULT
>>> and DT_NOGRAPHIC) to use two underscores and make them negative,
>>> and set DT_NONE to 0.
>>>
>>> This should fix the issue of non-working sun serial console
>>> with the suggested replacement of -nographic which is
>>> -display none.
>>
>> Note that "-display none" and "-nographic" aren't exactly
>> equivalent -- the latter is an option which turns on a bunch
>> of behaviour including but not limited to "-display none".
>
> Exactly. See ab51b1d568e02c80b1abf9016bda3a86dc1db389
> for a bit more context of this.
>
>>> I'm not still sure we really want to check for display type
>>> in qemu-char.c where we allow/disallow signals delivery from
>>> terminal, -- for other display types (CURSES) this makes no
>>> good sense.
>>
>> ...in particular I don't think "-display none" should
>> mean "don't allow ctrl-c" (though -nographic should
>> continue to have that effect), and this patch currently
>> introduces that behaviour change.
>
> As Anthony said before, -nographic is legacy. So there should
> be some more modern way to control this. That's exactly the
> change which I don't like myself.
> But "don't allow ctrl-c"
> which is currently bound to -nographic is equally wrong.
What's wrong about that? Isn't Ctrl+C passed through to the guest in
-nographic mode? I don't see how any other mode inclusing daemonize
would need that.
Andreas
>
>>> + DT__DEFAULT = -1, /* private */
>> I think these could use a slightly longer comment than just "private",
>> eg "private, used internally by vl.c only".
>
> Okay.
>
>
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
next prev parent reply other threads:[~2013-06-28 11:45 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 12:34 [Qemu-devel] [PATCH] display: stop using DT_NOGRAPHIC, use DT_NONE Michael Tokarev
2013-06-28 10:38 ` Michael Tokarev
2013-06-28 11:24 ` Peter Maydell
2013-06-28 11:29 ` Michael Tokarev
2013-06-28 11:34 ` Peter Maydell
2013-06-28 11:43 ` Michael Tokarev
2013-06-28 11:50 ` Peter Maydell
2013-06-28 12:05 ` Paolo Bonzini
2013-06-28 11:45 ` Andreas Färber [this message]
2013-06-28 11:50 ` Michael Tokarev
2013-06-28 11:55 ` Peter Maydell
2013-06-28 12:05 ` Michael Tokarev
2013-06-28 12:06 ` Paolo Bonzini
2013-06-28 12:09 ` Peter Maydell
2013-06-28 11:56 ` Andreas Färber
2013-06-28 12:05 ` Andreas Färber
2013-06-28 12:11 ` Paolo Bonzini
2013-07-09 18:37 ` Anthony Liguori
2013-07-09 19:00 ` Michael Tokarev
2013-07-09 20:45 ` Anthony Liguori
2013-07-09 21:18 ` Peter Maydell
2013-07-09 21:24 ` Anthony Liguori
2013-07-09 21:36 ` Peter Maydell
2013-07-09 22:03 ` Anthony Liguori
2013-07-16 11:10 ` Michael Tokarev
2013-07-10 4:45 ` Michael Tokarev
2013-07-10 5:08 ` Michael Tokarev
2013-07-16 11:35 ` Peter Maydell
2013-07-10 4:18 ` Michael Tokarev
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=51CD775A.3070006@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=todd@fries.net \
/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).