From: Michael Tokarev <mjt@tls.msk.ru>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
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 15:43:17 +0400 [thread overview]
Message-ID: <51CD76D5.2050709@msgid.tls.msk.ru> (raw)
In-Reply-To: <CAFEAcA97rrRn0iySUKTGfyAbLyLpOLiA9dQUhUJwB=LaOjAtWg@mail.gmail.com>
28.06.2013 15:34, Peter Maydell wrote:
> On 28 June 2013 12:29, Michael Tokarev <mjt@tls.msk.ru> wrote:
>> 28.06.2013 15:24, Peter Maydell wrote:
>>> ...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.
>
> All I'm saying is that I use -display none and I like that
> it defaults to "ctrl-c works and kills qemu" and I don't
> want you to break that :-)
I'm not. Code in qemu-char.c:
static bool stdio_allow_signal;
static void qemu_chr_set_echo_stdio(CharDriverState *chr, bool echo)
{
...
/* if graphical mode, we allow Ctrl-C handling */
if (!stdio_allow_signal)
tty.c_lflag &= ~ISIG;
...
}
static CharDriverState *qemu_chr_open_stdio(ChardevStdio *opts)
{
...
stdio_allow_signal = display_type != DT_NOGRAPHIC;
if (opts->has_signal) {
stdio_allow_signal = opts->signal;
}
...
}
Note it is used only for stdio char device, like -serial stdio,
so if you _just_ use -display none, without -serial stdio, you
wont notice a change.
And note that original intention isn't exactly clear, either.
How it is related with, say, curses display which needs raw
keypresses?
Adding Paolo who wrote that code in bb002513.
Thanks,
/mjt
next prev parent reply other threads:[~2013-06-28 11:43 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 [this message]
2013-06-28 11:50 ` Peter Maydell
2013-06-28 12:05 ` Paolo Bonzini
2013-06-28 11:45 ` Andreas Färber
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=51CD76D5.2050709@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.