From: Eric Blake <eblake@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>, John Snow <jsnow@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] docs: add blkdebug block driver documentation
Date: Wed, 24 Sep 2014 11:12:34 -0600 [thread overview]
Message-ID: <5422FB82.9020407@redhat.com> (raw)
In-Reply-To: <1411551854-23025-1-git-send-email-stefanha@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
On 09/24/2014 03:44 AM, 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]
Thanks for the updates.
Reviewed-by: Eric Blake <eblake@redhat.com>
> +
> +The error injection engine has an integer called the "state" that always starts
> +initialized to 1. The state integer is internal to blkdebug and cannot be
> +observed from outside but rules can interact with it for powerful matching
> +behavior.
> +
We could always expose it and update the documentation in a later patch.
But it is fair to document the current state of things (current docs
are always better than no docs :)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
next prev parent reply other threads:[~2014-09-24 17:12 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
2014-09-24 17:12 ` Eric Blake [this message]
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=5422FB82.9020407@redhat.com \
--to=eblake@redhat.com \
--cc=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.