From: Michael Tokarev <mjt@tls.msk.ru>
To: qemu-devel <qemu-devel@nongnu.org>,
Michael Roth <mdroth@linux.vnet.ibm.com>,
Anthony Liguori <aliguori@us.ibm.com>
Subject: [Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon
Date: Wed, 03 Jul 2013 10:03:38 +0400 [thread overview]
Message-ID: <51D3BEBA.4080809@msgid.tls.msk.ru> (raw)
Before
commit bd5c51ee6c4f1c79cae5ad2516d711a27b4ea8ec
Author: Michael Roth <mdroth@linux.vnet.ibm.com>
Date: Fri Jun 7 15:19:53 2013 -0500
qemu-char: don't issue CHR_EVENT_OPEN in a BH
we had no echo by default with -nographic, and it gave
the prompt when switching to monitor:
$ qemu-system-x86_64 -nographic
_
(nothing is on the screen except the command line)
(Ctrl+A, c)
QEMU 1.5.0 monitor - type 'help' for more information
(qemu) _
After this patch, we now have:
$ qemu-system-x86_64 -nographic
QEMU 1.5.0 monitor - type 'help' for more information
(qemu)
_
(note the cursor position on the _next_ line after the prompt),
and the system is actually in "serial port" mode, not monitor
mode (you still need to hit Ctrl+A,c to switch to monitor).
Thanks,
/mjt
next reply other threads:[~2013-07-03 6:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 6:03 Michael Tokarev [this message]
2013-07-03 21:06 ` [Qemu-devel] moving CHR_EVENT_OPEN out of BH broke echo for muxed mon Michael Roth
2013-07-29 11:26 ` Michael Tokarev
2013-07-29 19:07 ` Michael Roth
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=51D3BEBA.4080809@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=aliguori@us.ibm.com \
--cc=mdroth@linux.vnet.ibm.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).