qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Max Reitz <mreitz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] qmp: Documentation for BLOCK_IMAGE_CORRUPTED
Date: Tue, 3 Sep 2013 15:56:51 +0200	[thread overview]
Message-ID: <20130903135651.GH2683@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1378216179-8438-1-git-send-email-mreitz@redhat.com>

Am 03.09.2013 um 15:49 hat Max Reitz geschrieben:
> Add an appropriate entry describing this event and its parameters into
> qmp-events.txt.
> 
> Signed-off-by: Max Reitz <mreitz@redhat.com>
> Reviewed-by: Eric Blake <eblake@redhat.com>
> ---
> v2:
>  - moved section to keep qmp-events.txt sorted

Reviewed-by: Kevin Wolf <kwolf@redhat.com>

Don't forget to keep both Stefan and me CCed for block layer patches.
This week Stefan handles the queue.

Kevin

>  QMP/qmp-events.txt | 22 ++++++++++++++++++++++
>  1 file changed, 22 insertions(+)
> 
> diff --git a/QMP/qmp-events.txt b/QMP/qmp-events.txt
> index 39b6016..4b24ec9 100644
> --- a/QMP/qmp-events.txt
> +++ b/QMP/qmp-events.txt
> @@ -18,6 +18,28 @@ Example:
>      "data": { "actual": 944766976 },
>      "timestamp": { "seconds": 1267020223, "microseconds": 435656 } }
>  
> +BLOCK_IMAGE_CORRUPTED
> +---------------------
> +
> +Emitted when a disk image is being marked corrupt.
> +
> +Data:
> +
> +- "device": Device name (json-string)
> +- "msg":    Informative message (e.g., reason for the corruption) (json-string)
> +- "offset": If the corruption resulted from an image access, this is the access
> +            offset into the image (json-int)
> +- "size":   If the corruption resulted from an image access, this is the access
> +            size (json-int)
> +
> +Example:
> +
> +{ "event": "BLOCK_IMAGE_CORRUPTED",
> +    "data": { "device": "ide0-hd0",
> +        "msg": "Prevented active L1 table overwrite", "offset": 196608,
> +        "size": 65536 },
> +    "timestamp": { "seconds": 1378126126, "microseconds": 966463 } }
> +
>  BLOCK_IO_ERROR
>  --------------
>  
> -- 
> 1.8.3.1
> 
> 

  reply	other threads:[~2013-09-03 13:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-03 13:49 [Qemu-devel] [PATCH v2] qmp: Documentation for BLOCK_IMAGE_CORRUPTED Max Reitz
2013-09-03 13:56 ` Kevin Wolf [this message]
2013-09-04 14:44 ` 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=20130903135651.GH2683@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=mreitz@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 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).