From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:41207) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bhSSb-0006cy-8X for qemu-devel@nongnu.org; Tue, 06 Sep 2016 22:19:34 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bhSSZ-0001uO-AU for qemu-devel@nongnu.org; Tue, 06 Sep 2016 22:19:32 -0400 Date: Wed, 7 Sep 2016 10:19:22 +0800 From: Fam Zheng Message-ID: <20160907021922.GB15671@lemon> References: <1470662013-19785-1-git-send-email-famz@redhat.com> <1470662013-19785-3-git-send-email-famz@redhat.com> <20160906161822.GG4667@noname.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160906161822.GG4667@noname.redhat.com> Subject: Re: [Qemu-devel] [PATCH v7 02/20] qapi: Add lock-mode in blockdev-add options List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Kevin Wolf Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org, rjones@redhat.com, John Snow , Jeff Cody , Markus Armbruster , Max Reitz , stefanha@redhat.com, den@openvz.org, pbonzini@redhat.com, berrange@redhat.com On Tue, 09/06 18:18, Kevin Wolf wrote: > Am 08.08.2016 um 15:13 hat Fam Zheng geschrieben: > > To allow overriding the default locking behavior when opening the image. > > > > Signed-off-by: Fam Zheng > > --- > > qapi/block-core.json | 19 ++++++++++++++++++- > > 1 file changed, 18 insertions(+), 1 deletion(-) > > > > diff --git a/qapi/block-core.json b/qapi/block-core.json > > index 5e2d7d7..d1eb197 100644 > > --- a/qapi/block-core.json > > +++ b/qapi/block-core.json > > @@ -2151,6 +2151,20 @@ > > '*debug-level': 'int' } } > > > > ## > > +# @BlockdevLockMode > > +# > > +# Describes how QEMU should lock the image. > > +# > > +# @off: Disabled > > +# @shared: Use shared lock for both RO and RW images. > > +# @auto: Use exclusive lock for RW images, and shared lock for RO images. > > +# > > +# Since: 2.7 > > +## > > +{ 'enum': 'BlockdevLockMode', > > + 'data': [ 'off', 'shared', 'auto' ] } > > You decided to drop 'exclusive'? Didn't we agree last time that we > should have both a real 'exclusive' and 'auto'? I must have misunderstood it. I can add exclusive back. Fam