From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:57374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZZajJ-0007CM-6x for qemu-devel@nongnu.org; Wed, 09 Sep 2015 04:27:47 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZZajH-0003Ty-6y for qemu-devel@nongnu.org; Wed, 09 Sep 2015 04:27:45 -0400 References: <1441183880-26993-1-git-send-email-wency@cn.fujitsu.com> <1441183880-26993-16-git-send-email-wency@cn.fujitsu.com> <55E72599.6080107@redhat.com> From: Wen Congyang Message-ID: <55EFED60.9090000@cn.fujitsu.com> Date: Wed, 9 Sep 2015 16:27:12 +0800 MIME-Version: 1.0 In-Reply-To: <55E72599.6080107@redhat.com> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 15/16] support replication driver in blockdev-add List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eric Blake , qemu devel , Fam Zheng , Max Reitz , Paolo Bonzini , Stefan Hajnoczi Cc: Kevin Wolf , qemu block , Jiang Yunhong , Dong Eddie , "Dr. David Alan Gilbert" , "Michael R. Hines" , Yang Hongyang On 09/03/2015 12:36 AM, Eric Blake wrote: > On 09/02/2015 02:51 AM, Wen Congyang wrote: >> Signed-off-by: Wen Congyang >> --- >> qapi/block-core.json | 18 ++++++++++++++++-- >> 1 file changed, 16 insertions(+), 2 deletions(-) >> >> diff --git a/qapi/block-core.json b/qapi/block-core.json >> index 96f0530..86275e3 100644 >> --- a/qapi/block-core.json >> +++ b/qapi/block-core.json >> @@ -1383,7 +1383,7 @@ >> 'dmg', 'file', 'ftp', 'ftps', 'host_cdrom', 'host_device', >> 'host_floppy', 'http', 'https', 'null-aio', 'null-co', 'parallels', >> 'qcow', 'qcow2', 'qed', 'quorum', 'raw', 'tftp', 'vdi', 'vhdx', >> - 'vmdk', 'vpc', 'vvfat', 'nbd' ] } >> + 'vmdk', 'vpc', 'vvfat', 'nbd', 'replication' ] } > > 'nbd' is not in the current qemu.git; which means your patch series > depends on a prerequisite series. Please mention that sort of > information in your cover letter. > > Please keep this enum in alphabetical order. > > Missing documentation under @drv of BlockDeviceInfo that this was > introduced in 2.5. OK > >> >> ## >> # @BlockdevOptionsBase >> @@ -1825,6 +1825,19 @@ >> { 'enum' : 'ReplicationMode', 'data' : [ 'primary', 'secondary' ] } >> >> ## >> +# @BlockdevOptionsReplication >> +# >> +# Driver specific block device options for replication >> +# >> +# @mode: the replication mode > > Can the mode be 'unprotected', or must it be 'primary' or 'secondary' > when first creating a replication BDS? I will check it, and fix it in the next version. > >> +# >> +# Since: 2.5 >> +## >> +{ 'struct': 'BlockdevOptionsReplication', >> + 'base': 'BlockdevOptionsGenericFormat', >> + 'data': { 'mode': 'ReplicationMode' } } >> + >> +## >> # @BlockdevOptions >> # >> # Options for creating a block device. >> @@ -1869,7 +1882,8 @@ >> 'vhdx': 'BlockdevOptionsGenericFormat', >> 'vmdk': 'BlockdevOptionsGenericCOWFormat', >> 'vpc': 'BlockdevOptionsGenericFormat', >> - 'vvfat': 'BlockdevOptionsVVFAT' >> + 'vvfat': 'BlockdevOptionsVVFAT', >> + 'replication':'BlockdevOptionsReplication' >> } } > > It helps to keep this alphabetical. > OK Thanks Wen Congyang