qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ari Sundholm <ari@tuxera.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Aapo Vienamo <aapo@tuxera.com>,
	qemu-block@nongnu.org, Kevin Wolf <kwolf@redhat.com>,
	Max Reitz <mreitz@redhat.com>,
	Markus Armbruster <armbru@redhat.com>"open list:Block layer
	core" <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v2 02/10] block: Add blklogwrites
Date: Thu, 7 Jun 2018 21:48:27 +0300	[thread overview]
Message-ID: <98fccefb-89ab-3d14-b838-4991ac302959@tuxera.com> (raw)
In-Reply-To: <337a4d38-397e-a251-b387-27034140d94d@redhat.com>

On 06/07/2018 09:32 PM, Eric Blake wrote:
> On 06/07/2018 09:40 AM, Ari Sundholm wrote:
>> From: Aapo Vienamo <aapo@tuxera.com>
>>
>> Implements a block device write logging system, similar to Linux kernel
>> device mapper dm-log-writes. The write operations that are performed
>> on a block device are logged to a file or another block device. The
>> write log format is identical to the dm-log-writes format. Currently,
>> log markers are not supported.
>>
>> This functionality can be used for crash consistency and fs consistency
>> testing. By implementing it in qemu, tests utilizing write logs can be
>> be used to test non-Linux drivers and older kernels.
>>
>> The implementation is based on the blkverify and blkdebug block drivers.
>>
>> Signed-off-by: Aapo Vienamo <aapo@tuxera.com>
>> Signed-off-by: Ari Sundholm <ari@tuxera.com>
>> ---
> 
>> +++ b/qapi/block-core.json
>> @@ -2429,12 +2429,12 @@
>>   # Since: 2.9
>>   ##
>>   { 'enum': 'BlockdevDriver',
> 
> Missing a comment:
> 
> # @blklogwrites: Since 3.0
> 

Thanks, will add in v4.

>> -  'data': [ 'blkdebug', 'blkverify', 'bochs', 'cloop', 'copy-on-read',
>> -            'dmg', 'file', 'ftp', 'ftps', 'gluster', 'host_cdrom',
>> -            'host_device', 'http', 'https', 'iscsi', 'luks', 'nbd', 
>> 'nfs',
>> -            'null-aio', 'null-co', 'nvme', 'parallels', 'qcow', 
>> 'qcow2', 'qed',
>> -            'quorum', 'raw', 'rbd', 'replication', 'sheepdog', 'ssh',
>> -            'throttle', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat', 'vxhs' 
>> ] }
>> +  'data': [ 'blkdebug', 'blklogwrites', 'blkverify', 'bochs', 'cloop',
>> +            'copy-on-read', 'dmg', 'file', 'ftp', 'ftps', 'gluster',
>> +            'host_cdrom', 'host_device', 'http', 'https', 'iscsi', 
>> 'luks',
>> +            'nbd', 'nfs', 'null-aio', 'null-co', 'nvme', 'parallels', 
>> 'qcow',
>> +            'qcow2', 'qed', 'quorum', 'raw', 'rbd', 'replication', 
>> 'sheepdog',
>> +            'ssh', 'throttle', 'vdi', 'vhdx', 'vmdk', 'vpc', 'vvfat', 
>> 'vxhs' ] }
>>   ##
>>   # @BlockdevOptionsFile:
>> @@ -2949,6 +2949,21 @@
>>               '*set-state': ['BlkdebugSetStateOptions'] } }
>>   ##
>> +# @BlockdevOptionsBlklogwrites:
>> +#
>> +# Driver specific block device options for blklogwrites.
>> +#
>> +# @raw:     block device
>> +#
>> +# @log:     block device used to log writes on @raw
>> +#
>> +# Since: foo
> 
> s/foo/3.0/
> 

Oops, this was a placeholder that I ended up forgetting about. Will be 
fixed in v4.

Thanks,
Ari Sundholm
ari@tuxera.com

>> +##
>> +{ 'struct': 'BlockdevOptionsBlklogwrites',
>> +  'data': { 'raw': 'BlockdevRef',
>> +            'log': 'BlockdevRef' } }
>> +
>> +##
>>   # @BlockdevOptionsBlkverify:
>>   #
>>   # Driver specific block device options for blkverify.
>> @@ -3443,6 +3458,7 @@
>>     'discriminator': 'driver',
>>     'data': {
>>         'blkdebug':   'BlockdevOptionsBlkdebug',
>> +      'blklogwrites': 'BlockdevOptionsBlklogwrites',
>>         'blkverify':  'BlockdevOptionsBlkverify',
>>         'bochs':      'BlockdevOptionsGenericFormat',
>>         'cloop':      'BlockdevOptionsGenericFormat',
>> @@ -3971,6 +3987,7 @@
>>     'discriminator': 'driver',
>>     'data': {
>>         'blkdebug':       'BlockdevCreateNotSupported',
>> +      'blklogwrites':   'BlockdevCreateNotSupported',
>>         'blkverify':      'BlockdevCreateNotSupported',
>>         'bochs':          'BlockdevCreateNotSupported',
>>         'cloop':          'BlockdevCreateNotSupported',
>>
> 

  reply	other threads:[~2018-06-07 18:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-07 14:40 [Qemu-devel] [PATCH v2 00/10] New block driver: blklogwrites Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 01/10] block: Move two block permission constants to the relevant enum Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 02/10] block: Add blklogwrites Ari Sundholm
2018-06-07 18:32   ` Eric Blake
2018-06-07 18:48     ` Ari Sundholm [this message]
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 03/10] block: Add a mechanism for passing a block driver a block configuration Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 04/10] hw/scsi/scsi-disk: Always apply block configuration to block driver Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 05/10] hw/ide/qdev: " Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 6/6] block/blklogwrites: Use the block device logical sector size when logging writes Ari Sundholm
2018-06-07 14:43   ` Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 06/10] hw/block/virtio-blk: Always apply block configuration to block driver Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 07/10] hw/block/nvme: " Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 08/10] hw/block/fdc: " Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 09/10] block/blklogwrites: Use block limits from the backend block configuration Ari Sundholm
2018-06-07 14:40 ` [Qemu-devel] [PATCH v2 10/10] block/blklogwrites: Use the block device logical sector size when logging writes Ari Sundholm
2018-06-07 15:05 ` [Qemu-devel] [PATCH v2 00/10] New block driver: blklogwrites Ari Sundholm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=98fccefb-89ab-3d14-b838-4991ac302959@tuxera.com \
    --to=ari@tuxera.com \
    --cc=aapo@tuxera.com \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).