From: Kevin Wolf <kwolf@redhat.com>
To: Adam Litke <agl@us.ibm.com>
Cc: Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] New API for asynchronous monitor commands (V2)
Date: Thu, 28 Jan 2010 19:29:22 +0100 [thread overview]
Message-ID: <4B61D782.1010800@redhat.com> (raw)
In-Reply-To: <1264443524.2890.3.camel@aglitke>
Am 25.01.2010 19:18, schrieb Adam Litke:
> Changes since V1:
> - Miscellaneous code cleanups (Thanks Luiz)
>
> Qemu has a number of commands that can operate asynchronously (savevm, migrate,
> etc) and it will be getting more. For these commands, the user monitor needs
> to be suspended, but QMP monitors could continue to to accept other commands.
> This patch introduces a new command API that isolates the details of handling
> different monitor types from the actual command execution.
>
> A monitor command can use this API by implementing the mhandler.cmd_async
> handler (or info_async if appropriate). This function is responsible for
> submitting the command and does not return any data although it may raise
> errors. When the command completes, the QMPCompletion callback should be
> invoked with its opaque data and the command result.
>
> The process for submitting and completing an asynchronous command is different
> for QMP and user monitors. A user monitor must be suspended at submit time and
> resumed at completion time. The user_print() function must be passed to the
> QMPCompletion callback so the result can be displayed properly. QMP monitors
> are simpler. No submit time setup is required. When the command completes,
> monitor_protocol_emitter() writes the result in JSON format.
>
> This API can also be used to implement synchronous commands. In this case, the
> cmd_async handler should immediately call the QMPCompletion callback. It is my
> hope that this new interface will work for all commands, leading to a
> drastically simplified monitor.c once all commands are ported.
>
> Thanks to Anthony for helping me out with the initial design.
>
> Signed-off-by: Adam Litke <agl@us.ibm.com>
This commit introduces a segfault on info pci for me. The following
patch seems to make it work again. Is it correct or is rather info pci
doing something wrong?
diff --git a/monitor.c b/monitor.c
index fbae5ce..22690c4 100644
--- a/monitor.c
+++ b/monitor.c
@@ -3700,7 +3700,12 @@ static void monitor_print_error(Monitor *mon)
static int is_async_return(const QObject *data)
{
- return data && qdict_haskey(qobject_to_qdict(data), "__mon_async");
+ const QDict *dict = NULL;
+
+ if (data != NULL) {
+ dict = qobject_to_qdict(data);
+ }
+ return dict && qdict_haskey(dict, "__mon_async");
}
static void monitor_call_handler(Monitor *mon, const mon_cmd_t *cmd,
Kevin
next prev parent reply other threads:[~2010-01-28 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 18:18 [Qemu-devel] [PATCH] New API for asynchronous monitor commands (V2) Adam Litke
2010-01-26 12:16 ` [Qemu-devel] " Luiz Capitulino
2010-01-27 0:07 ` [Qemu-devel] " Anthony Liguori
2010-01-28 18:29 ` Kevin Wolf [this message]
2010-01-28 18:37 ` Luiz Capitulino
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=4B61D782.1010800@redhat.com \
--to=kwolf@redhat.com \
--cc=agl@us.ibm.com \
--cc=avi@redhat.com \
--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).