qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH 6/7] blkdebug: Add events and rules
Date: Mon, 29 Mar 2010 10:00:46 +0200	[thread overview]
Message-ID: <4BB05E2E.5000108@redhat.com> (raw)
In-Reply-To: <20100328131210.GA13453@lst.de>

Am 28.03.2010 15:12, schrieb Christoph Hellwig:
> On Mon, Mar 15, 2010 at 06:08:34PM +0100, Kevin Wolf wrote:
>> +    fprintf(stderr, "bdrv_debug_event: %d\n", event);
> 
> Is this supposed to be in the final version or a leftover debugging aid?

It's not there in the final version (which I have already sent out, btw,
so you have reviewed an old version)

>> +#define BLKDBG_EVENT(bs, evt) bdrv_debug_event(bs, evt)
> 
> Why not call bdrv_debug_event directly?

Originally I had intended to add a flag to ./configure to enable
blkdebug and #ifdef this out if it's not compiled in. Maybe we still
want to add that, but then it's not really much that you save.

>> +    config = strdup(filename);
>> +    config[c - filename] = '\0';
>> +    ret = read_config(s, config);
>> +    if (ret < 0) {
>> +        return ret;
>> +    }
>> +    filename = c + 1;
>> +
>> +    /* Open the backing file */
>> +    ret = bdrv_file_open(&s->hd, filename, flags);
>> +    if (ret < 0) {
>> +        return ret;
>> +    }
>> +
>> +    return 0;
> 
> Don't we need to free config somewhere?

Oops, this one is still there in the final version. I'll send another
version of the series.

Kevin

  reply	other threads:[~2010-03-29  8:01 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-15 17:08 [Qemu-devel] [RFC][PATCH 0/7] blkdebug Kevin Wolf
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 1/7] qemu-config: qemu_read_config_file() reads the normal config file Kevin Wolf
2010-03-28 12:19   ` Christoph Hellwig
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 2/7] qemu-config: Make qemu_config_parse more generic Kevin Wolf
2010-03-28 12:20   ` Christoph Hellwig
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 3/7] blkdebug: Basic request passthrough Kevin Wolf
2010-03-28 12:24   ` Christoph Hellwig
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 4/7] blkdebug: Inject errors Kevin Wolf
2010-03-28 12:25   ` Christoph Hellwig
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 5/7] Make qemu-config available for tools Kevin Wolf
2010-03-28 12:34   ` Christoph Hellwig
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 6/7] blkdebug: Add events and rules Kevin Wolf
2010-03-28 13:12   ` Christoph Hellwig
2010-03-29  8:00     ` Kevin Wolf [this message]
2010-03-15 17:08 ` [Qemu-devel] [RFC][PATCH 7/7] qcow2: Trigger blkdebug events Kevin Wolf
2010-03-28 13:22   ` Christoph Hellwig
2010-03-15 17:40 ` [Qemu-devel] [RFC][PATCH 0/7] blkdebug Blue Swirl
2010-03-15 17:55   ` Kevin Wolf
2010-03-15 18:17     ` Blue Swirl

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=4BB05E2E.5000108@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hch@lst.de \
    --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).