From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v4] blkverify: Add block driver for verifying I/O
Date: Tue, 21 Sep 2010 16:26:01 +0200 [thread overview]
Message-ID: <4C98C079.6070404@redhat.com> (raw)
In-Reply-To: <1285073062-5317-1-git-send-email-stefanha@linux.vnet.ibm.com>
Am 21.09.2010 14:44, schrieb Stefan Hajnoczi:
> The blkverify block driver makes investigating image format data
> corruption much easier. A raw image initialized with the same contents
> as the test image (e.g. qcow2 file) must be provided. The raw image
> mirrors read/write operations and is used to verify that data read from
> the test image is correct.
>
> See docs/blkverify.txt for more information.
>
> Signed-off-by: Stefan Hajnoczi <stefanha@linux.vnet.ibm.com>
Heh, so four versions is actually not enough. This breaks the mingw32
build (EINPROGESS is not defined).
Kevin
next prev parent reply other threads:[~2010-09-21 14:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-21 12:44 [Qemu-devel] [PATCH v4] blkverify: Add block driver for verifying I/O Stefan Hajnoczi
2010-09-21 13:33 ` [Qemu-devel] " Kevin Wolf
2010-09-21 14:26 ` Kevin Wolf [this message]
2010-09-21 14:38 ` Stefan Hajnoczi
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=4C98C079.6070404@redhat.com \
--to=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.