From: Kevin Wolf <kwolf@redhat.com>
To: Luiz Capitulino <lcapitulino@redhat.com>
Cc: fromani@redhat.com, armbru@redhat.com,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] block: extend BLOCK_IO_ERROR with reason string
Date: Thu, 11 Sep 2014 16:36:58 +0200 [thread overview]
Message-ID: <20140911143658.GF3891@noname.redhat.com> (raw)
In-Reply-To: <20140911102548.3a270709@redhat.com>
Am 11.09.2014 um 16:25 hat Luiz Capitulino geschrieben:
> BLOCK_IO_ERROR events are logged by libvirt, which helps with
> post mortem analysis of guests. However, one information that
> we miss today is a human readable string describing the cause
> of the I/O error.
>
> This commit adds that string it to BLOCK_IO_ERROR. Note that
> this string is a debugging aid for humans, meaning that it
> should not parsed by applications.
>
> Signed-off-by: Luiz Capitulino <lcapitulino@redhat.com>
Thanks, applied to the block branch.
Kevin
next prev parent reply other threads:[~2014-09-11 14:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 14:25 [Qemu-devel] [PATCH] block: extend BLOCK_IO_ERROR with reason string Luiz Capitulino
2014-09-11 14:36 ` Kevin Wolf [this message]
2014-09-11 15:11 ` Eric Blake
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=20140911143658.GF3891@noname.redhat.com \
--to=kwolf@redhat.com \
--cc=armbru@redhat.com \
--cc=fromani@redhat.com \
--cc=lcapitulino@redhat.com \
--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).