From patchwork Mon Nov 30 11:32:20 2015 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Peter Xu X-Patchwork-Id: 549951 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from lists.gnu.org (lists.gnu.org [IPv6:2001:4830:134:3::11]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 6C60E140187 for ; Mon, 30 Nov 2015 22:35:19 +1100 (AEDT) Received: from localhost ([::1]:40248 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3Mjl-0002hz-8A for incoming@patchwork.ozlabs.org; Mon, 30 Nov 2015 06:35:17 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35725) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3MjI-0001sB-2T for qemu-devel@nongnu.org; Mon, 30 Nov 2015 06:34:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a3MjD-0005Ga-Va for qemu-devel@nongnu.org; Mon, 30 Nov 2015 06:34:48 -0500 Received: from mx1.redhat.com ([209.132.183.28]:50936) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a3MjD-0005GW-RX for qemu-devel@nongnu.org; Mon, 30 Nov 2015 06:34:43 -0500 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (Postfix) with ESMTPS id 9508BC0D223A for ; Mon, 30 Nov 2015 11:34:43 +0000 (UTC) Received: from pxdev.xzpeter.org.com (vpn1-4-252.pek2.redhat.com [10.72.4.252]) by int-mx11.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id tAUBWRj2012457; Mon, 30 Nov 2015 06:34:34 -0500 From: Peter Xu To: qemu-devel@nongnu.org Date: Mon, 30 Nov 2015 19:32:20 +0800 Message-Id: <1448883140-20249-13-git-send-email-peterx@redhat.com> In-Reply-To: <1448883140-20249-1-git-send-email-peterx@redhat.com> References: <1448883140-20249-1-git-send-email-peterx@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.24 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 209.132.183.28 Cc: drjones@redhat.com, lersek@redhat.com, armbru@redhat.com, peterx@redhat.com, lcapitulino@redhat.com, famz@redhat.com, pbonzini@redhat.com Subject: [Qemu-devel] [PATCH v3 12/12] Dump: enhance the documentations. X-BeenThere: qemu-devel@nongnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Sender: qemu-devel-bounces+incoming=patchwork.ozlabs.org@nongnu.org Add more documents to mention about "query-dump" and DUMP_COMPLETED events. Signed-off-by: Peter Xu --- qapi-schema.json | 7 +++++-- qmp-commands.hx | 4 +++- 2 files changed, 8 insertions(+), 3 deletions(-) diff --git a/qapi-schema.json b/qapi-schema.json index 577c381..ce4acb2 100644 --- a/qapi-schema.json +++ b/qapi-schema.json @@ -2115,8 +2115,11 @@ # 2. fd: the protocol starts with "fd:", and the following string # is the fd's name. # -# @detach: #optional if true, QMP will return immediately rather than -# waiting dump to be finished (since 2.6). +# @detach: #optional if true, QMP will return immediately rather +# than waiting dump to be finished. If this is specified, +# user could later use "query-dump" to check latest dump +# status. When dump finishes, one event DUMP_COMPLETED will +# be sent to the user to notify the completion (since 2.6). # # @begin: #optional if specified, the starting physical address. # diff --git a/qmp-commands.hx b/qmp-commands.hx index ac6d2da..cd097d4 100644 --- a/qmp-commands.hx +++ b/qmp-commands.hx @@ -858,7 +858,9 @@ Arguments: - "protocol": destination file(started with "file:") or destination file descriptor (started with "fd:") (json-string) - "detach": if specificed, command will return immediately, without waiting - for dump to be finished (json-bool) + for dump to be finished. After command return, user + could query for latest dump status using "query-dump". When dump + finishes, an event DUMP_COMPLETED will be sent (json-bool) - "begin": the starting physical address. It's optional, and should be specified with length together (json-int) - "length": the memory size, in bytes. It's optional, and should be specified