From: John Snow <jsnow@redhat.com>
To: Max Reitz <mreitz@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] docs: add blkdebug block driver documentation
Date: Wed, 24 Sep 2014 12:26:09 -0400 [thread overview]
Message-ID: <5422F0A1.50408@redhat.com> (raw)
In-Reply-To: <5422F03E.3080409@redhat.com>
On 09/24/2014 12:24 PM, Max Reitz wrote:
> On 24.09.2014 11:44, Stefan Hajnoczi wrote:
>> The blkdebug block driver is undocumented. Documenting it is worthwhile
>> since it offers powerful error injection features that are used by
>> qemu-iotests test cases.
>>
>> This document will make it easier for people to learn about and use
>> blkdebug.
>>
>> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>> v3:
>> * Fix tab space damage [Eric]
>> * Rephrase event_names[] as full list of events [Eric]
>> * Explain that blkdebug state is not observable from outside [Eric]
>> * Clarify state 0 and state 1 [Eric]
>>
>> v2:
>> * Added GPL v2 or later license and Red Hat copyright [Eric]
>> * Expanded ini rules file explanation [Paolo]
>> * Added note that errno values depend on the host [Eric]
>>
>> docs/blkdebug.txt | 161
>> ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 161 insertions(+)
>> create mode 100644 docs/blkdebug.txt
>
> Reviewed-by: Max Reitz <mreitz@redhat.com>
>
> Maybe I'll add information about blkdebug's QMP interface sometime...
If you have the cycles and the knowledge, you definitely should!
next prev parent reply other threads:[~2014-09-24 16:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 9:44 [Qemu-devel] [PATCH v3] docs: add blkdebug block driver documentation Stefan Hajnoczi
2014-09-24 15:43 ` Benoît Canet
2014-09-24 16:24 ` Max Reitz
2014-09-24 16:26 ` John Snow [this message]
2014-09-24 17:12 ` Eric Blake
2014-09-25 7:41 ` Kevin Wolf
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=5422F0A1.50408@redhat.com \
--to=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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.