[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] Re: [PATCH] New API for asynchronous monitor commands (V2)
From: |
Luiz Capitulino |
Subject: |
[Qemu-devel] Re: [PATCH] New API for asynchronous monitor commands (V2) |
Date: |
Tue, 26 Jan 2010 10:16:34 -0200 |
On Mon, 25 Jan 2010 12:18:44 -0600
Adam Litke <address@hidden> wrote:
> 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.
s/QMPCompletion/MonitorCompletion
Otherwise looks good to me.