qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Max Reitz <mreitz@redhat.com>
To: Eric Blake <eblake@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Peter Lieven <pl@kamp.de>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] qapi: Complete BlkdebugEvent
Date: Fri, 07 Nov 2014 22:01:55 +0100	[thread overview]
Message-ID: <545D3343.9000203@redhat.com> (raw)
In-Reply-To: <545D3247.9040905@redhat.com>

On 07.11.2014 21:57, Eric Blake wrote:
> On 11/07/2014 04:51 PM, Max Reitz wrote:
>> Several events were missing from the QAPI enum, add them.
>>
>> Reported-by: Kevin Wolf <kwolf@redhat.com>
>> Signed-off-by: Max Reitz <mreitz@redhat.com>
>> ---
>>   qapi/block-core.json | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
> Do we need any documentation on these? Or is this one of those types
> where the only people using it are already expected to be familiar with
> the C code?

Well, you have to be familiar with the block driver as well. The 
documentation wouldn't be very useful, it'd be something like 
"refblock_alloc.write_blocks: Emitted when the new refblocks are written 
during qcow2 refblock allocation" or "empty_image_prepare: Emitted when 
qcow2 prepares to empty an image". So I'd leave the documentation out. 
Most users don't want to use this anyway, blkdebug is for debugging 
purposes only, so you need to know what the event does in the context of 
the block driver you're debugging anyway.

Max

>> diff --git a/qapi/block-core.json b/qapi/block-core.json
>> index 77a0cfb..8c3e45d 100644
>> --- a/qapi/block-core.json
>> +++ b/qapi/block-core.json
>> @@ -1422,7 +1422,9 @@
>>               'refblock_alloc.write_blocks', 'refblock_alloc.write_table',
>>               'refblock_alloc.switch_table', 'cluster_alloc',
>>               'cluster_alloc_bytes', 'cluster_free', 'flush_to_os',
>> -            'flush_to_disk' ] }
>> +            'flush_to_disk', 'pwritev_rmw.head', 'pwritev_rmw.after_head',
>> +            'pwritev_rmw.tail', 'pwritev_rmw.after_tail', 'pwritev',
>> +            'pwritev_zero', 'pwritev_done', 'empty_image_prepare' ] }
>>   
>>   ##
>>   # @BlkdebugInjectErrorOptions
>>

      reply	other threads:[~2014-11-07 21:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07 15:51 [Qemu-devel] [PATCH] qapi: Complete BlkdebugEvent Max Reitz
2014-11-07 16:52 ` Kevin Wolf
2014-11-07 20:57 ` Eric Blake
2014-11-07 21:01   ` Max Reitz [this message]

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=545D3343.9000203@redhat.com \
    --to=mreitz@redhat.com \
    --cc=eblake@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=pl@kamp.de \
    --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).