From patchwork Fri May 4 20:20:21 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Luiz Capitulino X-Patchwork-Id: 156986 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Received: from lists.gnu.org (lists.gnu.org [208.118.235.17]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 2F5E0B707A for ; Sat, 5 May 2012 06:47:21 +1000 (EST) Received: from localhost ([::1]:42931 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQOzz-0005r8-Pu for incoming@patchwork.ozlabs.org; Fri, 04 May 2012 16:21:07 -0400 Received: from eggs.gnu.org ([208.118.235.92]:35156) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQOzd-0004ta-Nx for qemu-devel@nongnu.org; Fri, 04 May 2012 16:20:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SQOzb-0006NK-R4 for qemu-devel@nongnu.org; Fri, 04 May 2012 16:20:45 -0400 Received: from mx1.redhat.com ([209.132.183.28]:46830) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SQOzb-0006N3-IN for qemu-devel@nongnu.org; Fri, 04 May 2012 16:20:43 -0400 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id q44KKb9e012742 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Fri, 4 May 2012 16:20:37 -0400 Received: from localhost (ovpn-116-75.ams2.redhat.com [10.36.116.75]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id q44KKZpr017172; Fri, 4 May 2012 16:20:36 -0400 From: Luiz Capitulino To: qemu-devel@nongnu.org Date: Fri, 4 May 2012 17:20:21 -0300 Message-Id: <1336162822-13161-6-git-send-email-lcapitulino@redhat.com> In-Reply-To: <1336162822-13161-1-git-send-email-lcapitulino@redhat.com> References: <1336162822-13161-1-git-send-email-lcapitulino@redhat.com> X-Scanned-By: MIMEDefang 2.68 on 10.5.11.23 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.132.183.28 Cc: pbonzini@redhat.com, mdroth@linux.vnet.ibm.com, mprivozn@redhat.com Subject: [Qemu-devel] [PATCH 5/6] qemu-ga: guest-suspend-ram: don't emit a success response 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 Today, qemu-ga may not be able to emit a success response when guest-suspend-ram completes. This happens because the VM may suspend before qemu-ga is able to emit a response. This semantic is a bit confusing, as it's not clear for clients if they should wait for a response or how they should check for success. This commit solves that problem by changing guest-suspend-ram to never emit a success response and suggests in the documentation what clients should do to check for success. Signed-off-by: Luiz Capitulino --- qapi-schema-guest.json | 15 +++++++++------ 1 file changed, 9 insertions(+), 6 deletions(-) diff --git a/qapi-schema-guest.json b/qapi-schema-guest.json index 8ea7805..f5f6f26 100644 --- a/qapi-schema-guest.json +++ b/qapi-schema-guest.json @@ -391,17 +391,20 @@ # command. Thus, it's *required* to query QEMU for the presence of the # 'system_wakeup' command before issuing guest-suspend-ram. # -# Returns: nothing on success +# Returns: This command does NOT return a response on success. There are +# two options to check for success: +# 1. Wait for the SUSPEND QMP event from QEMU +# 2. Check for the suspended RunState in QEMU, by issuing query-status +# +# The following errors may be returned: # If suspend to ram is not supported, Unsupported # -# Notes: o This is an asynchronous request. There's no guarantee a response -# will be sent -# o It's strongly recommended to issue the guest-sync command before -# sending commands when the guest resumes +# Notes: It's strongly recommended to issue the guest-sync command before +# sending commands when the guest resumes # # Since: 1.1 ## -{ 'command': 'guest-suspend-ram' } +{ 'command': 'guest-suspend-ram', 'success-response': 'no' } ## # @guest-suspend-hybrid