From: Paolo Bonzini <pbonzini@redhat.com>
To: qemu-devel@nongnu.org
Cc: kraxel@redhat.com
Subject: [Qemu-devel] [PATCH 0/3] another round of qemu-char fixes
Date: Tue, 16 Apr 2013 13:10:39 +0200 [thread overview]
Message-ID: <1366110642-22095-1-git-send-email-pbonzini@redhat.com> (raw)
I'm happy to say that I'm not touching IOWatchPoll (well, almost: only
for consistency). Instead, these patches try to make the code consistent
(thus avoiding CRITICAL messages from glib) and to fix detection of pty
connections; Gerd reported that it went berserk with polling. I think it
is the same failure reported by Michael Hines, but I couldn't reproduce
it with "-serial pty", only with the monitor.
Paolo Bonzini (3):
qemu-char: use consistent idiom for removing sources
qemu-char: simplify pty polling
qemu-char: correct return value from chr_read functions
qemu-char.c | 95 ++++++++++++++++++++++++++++++++++++-------------------------
1 file changed, 56 insertions(+), 39 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-04-16 11:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-16 11:10 Paolo Bonzini [this message]
2013-04-16 11:10 ` [Qemu-devel] [PATCH 1/3] qemu-char: use consistent idiom for removing sources Paolo Bonzini
2013-04-16 11:10 ` [Qemu-devel] [PATCH 2/3] qemu-char: simplify pty polling Paolo Bonzini
2013-04-16 11:10 ` [Qemu-devel] [PATCH 3/3] qemu-char: correct return value from chr_read functions Paolo Bonzini
2013-04-16 11:22 ` [Qemu-devel] [PATCH 0/3] another round of qemu-char fixes Gerd Hoffmann
2013-04-17 7:06 ` Gerd Hoffmann
2013-04-17 9:28 ` Paolo Bonzini
2013-04-17 10:17 ` Paolo Bonzini
2013-04-18 6:14 ` Gerd Hoffmann
2013-04-18 12:38 ` Paolo Bonzini
2013-04-18 12:54 ` Gerd Hoffmann
2013-04-18 13:11 ` Paolo Bonzini
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=1366110642-22095-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=kraxel@redhat.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).