From: Wenchao Xia <xiawenc@linux.vnet.ibm.com>
To: qemu-devel@nongnu.org
Cc: Wenchao Xia <xiawenc@linux.vnet.ibm.com>,
aliguori@us.ibm.com, armbru@redhat.com, chenwj@iis.sinica.edu.tw,
lcapitulino@redhat.com
Subject: [Qemu-devel] [PATCH V5 0/6] HMP: allow parsing for sub command
Date: Fri, 11 Jan 2013 17:13:59 +0800 [thread overview]
Message-ID: <1357895645-30359-1-git-send-email-xiawenc@linux.vnet.ibm.com> (raw)
These patches enhance HMP to allow it parse 2nd level of commands, such
as info sub command list, which means foldered command with parameter is
possible now.
V2:
Follow the way supposed by Markus, which make the infrastructure knows
there is possible a 2nd level of command exist, instead of a hack. In this
way extention of command folder level is easy.
Moved function declaration and better doc according to comments.
Removed the patch about info snapshots, which will goto another serial.
V3:
Split out code moving patch.
V4:
Removed change of qmp_find_cmd().
Removed name change of monitor_parse_command().
v5:
Eliminate 'info' in mhandler for that it have same format with 'cmd' and info
is not a special case but a sub-command now.
Split out patch that checking for space before check for sub-command.
Better comments for monitor_parse_command().
Add parameter start for better error tips in sub-command case.
Add comments about how sub_table and mhandler interact.
Better commit message and tips that "info <unknowns>" show error now.
Wenchao Xia (6):
HMP: add QDict to info callback handler
HMP: delete info handler
HMP: add infrastructure for sub command
HMP: filter out space before check of sub-command
HMP: move define of mon_cmds
HMP: add sub command table to info
hmp-commands.hx | 3 +-
hmp.c | 36 ++++----
hmp.h | 36 ++++----
hw/i8259.c | 4 +-
hw/lm32_pic.c | 4 +-
hw/lm32_pic.h | 4 +-
hw/loader.c | 2 +-
hw/loader.h | 3 +-
hw/pc.h | 4 +-
hw/pcmcia.h | 2 +-
hw/qdev-monitor.c | 4 +-
hw/qdev-monitor.h | 4 +-
hw/sun4m.c | 4 +-
hw/sun4m.h | 4 +-
hw/usb.h | 2 +-
hw/usb/bus.c | 2 +-
hw/usb/host-bsd.c | 2 +-
hw/usb/host-linux.c | 2 +-
include/net/net.h | 2 +-
include/net/slirp.h | 2 +-
include/sysemu/sysemu.h | 4 +-
monitor.c | 202 ++++++++++++++++++++++++----------------------
net/net.c | 2 +-
net/slirp.c | 2 +-
savevm.c | 2 +-
vl.c | 2 +-
26 files changed, 175 insertions(+), 165 deletions(-)
next reply other threads:[~2013-01-11 9:16 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-11 9:13 Wenchao Xia [this message]
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 1/6] HMP: add QDict to info callback handler Wenchao Xia
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 2/6] HMP: delete info handler Wenchao Xia
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 3/6] HMP: add infrastructure for sub command Wenchao Xia
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 4/6] HMP: filter out space before check of sub-command Wenchao Xia
2013-01-11 20:12 ` Luiz Capitulino
2013-01-14 2:11 ` Wenchao Xia
2013-01-14 13:46 ` Markus Armbruster
2013-01-14 15:33 ` Luiz Capitulino
2013-01-15 3:06 ` Wenchao Xia
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 5/6] HMP: move define of mon_cmds Wenchao Xia
2013-01-11 9:14 ` [Qemu-devel] [PATCH V5 6/6] HMP: add sub command table to info Wenchao Xia
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=1357895645-30359-1-git-send-email-xiawenc@linux.vnet.ibm.com \
--to=xiawenc@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=armbru@redhat.com \
--cc=chenwj@iis.sinica.edu.tw \
--cc=lcapitulino@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).