From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50867) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYk7n-0005wh-1M for qemu-devel@nongnu.org; Wed, 24 Feb 2016 19:49:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aYk7i-0005Kr-D9 for qemu-devel@nongnu.org; Wed, 24 Feb 2016 19:49:46 -0500 Received: from [59.151.112.132] (port=58311 helo=heian.cn.fujitsu.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aYk7h-0005BS-ST for qemu-devel@nongnu.org; Wed, 24 Feb 2016 19:49:42 -0500 References: <1456308715-15465-1-git-send-email-xiecl.fnst@cn.fujitsu.com> <1456308715-15465-3-git-send-email-xiecl.fnst@cn.fujitsu.com> <56CDE156.3020703@redhat.com> From: Wen Congyang Message-ID: <56CE4FC8.5060605@cn.fujitsu.com> Date: Thu, 25 Feb 2016 08:50:16 +0800 MIME-Version: 1.0 In-Reply-To: <56CDE156.3020703@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v5 2/3] qmp event: Refactor QUORUM_REPORT_BAD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , Changlong Xie , qemu devel , Alberto Garcia , Kevin Wolf , Max Reitz , Markus Armbruster Cc: "Dr. David Alan Gilbert" On 02/25/2016 12:59 AM, Eric Blake wrote: > On 02/24/2016 03:11 AM, Changlong Xie wrote: >> Introduce QuorumOpType, and make QUORUM_REPORT_BAD compatible >> with it. >> >> Cc: Dr. David Alan Gilbert >> Cc: Wen Congyang >> Signed-off-by: Wen Congyang >> Signed-off-by: Changlong Xie >> --- > >> +++ b/docs/qmp-events.txt >> @@ -307,6 +307,7 @@ Emitted to report a corruption of a Quorum file. >> >> Data: >> >> +- "type": Quorum operation type (json-string, optional) > > I don't think 'type' needs to be optional, after all. Just always > output it. If we output read/write type, old libvirt will ignore the read/write error events? Thanks Wen Congyang > >> - "error": Error message (json-string, optional) >> Only present on failure. This field contains a human-readable >> error message. There are no semantics other than that the >> @@ -318,10 +319,17 @@ Data: >> >> Example: >> >> +Read/Write operation: >> { "event": "QUORUM_REPORT_BAD", >> "data": { "node-name": "node0", "sector-num": 345435, "sectors-count": 5 }, >> "timestamp": { "seconds": 1344522075, "microseconds": 745528 } } > > and this example would then show "type":"read" >