From: Luiz Capitulino <lcapitulino@redhat.com>
To: qemu-devel@nongnu.org
Cc: armbru@redhat.com, aliguori@us.ibm.com, kraxel@redhat.com,
fred.konrad@greensocs.com
Subject: [Qemu-devel] [PATCH v2 0/4] Monitor: make output buffer dynamic
Date: Tue, 2 Apr 2013 16:18:13 -0400 [thread overview]
Message-ID: <1364933897-25803-1-git-send-email-lcapitulino@redhat.com> (raw)
Hi,
This series does two things: it makes the Monitor's output buffer dynamic
(so that we fix an assertion bug in the Monitor); and it also switches
the human-monitor-command command to use that buffer instead of the
Memory chardev driver, which is dropped.
Most important details in patches 2/4 and 3/4.
o v2
- Switch human-monitor-command to the dynamic buffer
- Drop the Memory chardev driver
Luiz Capitulino (4):
qstring: add qstring_get_length()
Monitor: Make output buffer dynamic
hmp: human-monitor-command: stop using the Memory chardev driver
chardev: drop the Memory chardev driver
include/qapi/qmp/qstring.h | 1 +
monitor.c | 60 +++++++++++++++++++++++++------------------
qemu-char.c | 64 ----------------------------------------------
qobject/qstring.c | 8 ++++++
4 files changed, 44 insertions(+), 89 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-04-02 20:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-02 20:18 Luiz Capitulino [this message]
2013-04-02 20:18 ` [Qemu-devel] [PATCH 1/4] qstring: add qstring_get_length() Luiz Capitulino
2013-04-02 20:18 ` [Qemu-devel] [PATCH 2/4] Monitor: Make output buffer dynamic Luiz Capitulino
2013-04-02 20:48 ` Eric Blake
2013-04-02 20:18 ` [Qemu-devel] [PATCH 3/4] hmp: human-monitor-command: stop using the Memory chardev driver Luiz Capitulino
2013-04-02 20:44 ` Eric Blake
2013-04-03 13:33 ` Luiz Capitulino
2013-04-02 20:18 ` [Qemu-devel] [PATCH 4/4] chardev: drop " Luiz Capitulino
2013-04-02 20:50 ` Eric Blake
2013-04-03 8:23 ` [Qemu-devel] [PATCH v2 0/4] Monitor: make output buffer dynamic Gerd Hoffmann
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=1364933897-25803-1-git-send-email-lcapitulino@redhat.com \
--to=lcapitulino@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=fred.konrad@greensocs.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).