qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anton Nefedov <anton.nefedov@virtuozzo.com>
To: qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org, kwolf@redhat.com, mreitz@redhat.com,
	eblake@redhat.com, den@virtuozzo.com, berto@igalia.com,
	Anton Nefedov <anton.nefedov@virtuozzo.com>
Subject: [Qemu-devel] [PATCH v8 2/9] blkverify: set supported write/zero flags
Date: Mon, 12 Mar 2018 13:16:51 +0300	[thread overview]
Message-ID: <1520849818-6915-3-git-send-email-anton.nefedov@virtuozzo.com> (raw)
In-Reply-To: <1520849818-6915-1-git-send-email-anton.nefedov@virtuozzo.com>

Signed-off-by: Anton Nefedov <anton.nefedov@virtuozzo.com>
Reviewed-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Max Reitz <mreitz@redhat.com>
---
 block/blkverify.c | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/block/blkverify.c b/block/blkverify.c
index 331365b..de2fdc1 100644
--- a/block/blkverify.c
+++ b/block/blkverify.c
@@ -141,6 +141,15 @@ static int blkverify_open(BlockDriverState *bs, QDict *options, int flags,
         goto fail;
     }
 
+    bs->supported_write_flags = BDRV_REQ_FUA &
+        bs->file->bs->supported_write_flags &
+        s->test_file->bs->supported_write_flags;
+
+    bs->supported_zero_flags =
+        (BDRV_REQ_FUA | BDRV_REQ_MAY_UNMAP) &
+        bs->file->bs->supported_zero_flags &
+        s->test_file->bs->supported_zero_flags;
+
     ret = 0;
 fail:
     qemu_opts_del(opts);
-- 
2.7.4

  parent reply	other threads:[~2018-03-12 10:17 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 10:16 [Qemu-devel] [PATCH v8 0/9] qcow2: cluster space preallocation Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 1/9] mirror: inherit supported write/zero flags Anton Nefedov
2018-03-16 10:35   ` Alberto Garcia
2018-03-12 10:16 ` Anton Nefedov [this message]
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 3/9] quorum: set " Anton Nefedov
2018-03-16 10:39   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 4/9] block: introduce BDRV_REQ_ALLOCATE flag Anton Nefedov
2018-03-16 11:01   ` Alberto Garcia
2018-03-16 14:52     ` Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 5/9] block: treat BDRV_REQ_ALLOCATE as serialising Anton Nefedov
2018-03-19 11:02   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 6/9] file-posix: support BDRV_REQ_ALLOCATE Anton Nefedov
2018-03-16 14:53   ` Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 7/9] block: support BDRV_REQ_ALLOCATE in passthrough drivers Anton Nefedov
2018-03-16 11:03   ` Alberto Garcia
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 8/9] qcow2: skip writing zero buffers to empty COW areas Anton Nefedov
2018-03-16 13:58   ` Alberto Garcia
2018-03-16 15:09     ` Anton Nefedov
2018-03-12 10:16 ` [Qemu-devel] [PATCH v8 9/9] iotest 134: test cluster-misaligned encrypted write Anton Nefedov

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=1520849818-6915-3-git-send-email-anton.nefedov@virtuozzo.com \
    --to=anton.nefedov@virtuozzo.com \
    --cc=berto@igalia.com \
    --cc=den@virtuozzo.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).