All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Kevin Wolf <kwolf@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Test L1 table growth
Date: Tue, 7 Jul 2009 12:28:47 +0200	[thread overview]
Message-ID: <20090707102847.GA23964@lst.de> (raw)
In-Reply-To: <4A52FBE1.70302@redhat.com>

On Tue, Jul 07, 2009 at 09:40:17AM +0200, Kevin Wolf wrote:
> Ok, so using qemu in our tests is basically impossible because we can't
> get any status messages. Bad news.
> 
> For this one we can handle it differently: I'll implement
> bdrv_get/put_buffer in qemu-io, this should be more or less the same to
> the image format drivers. We even get more control over the data
> written, so I guess this is the better approach anyway.

Yes, that's a very good plan.

      reply	other threads:[~2009-07-07 10:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 13:59 [Qemu-devel] [PATCH] qemu-iotests: Test L1 table growth Kevin Wolf
2009-07-06 18:54 ` Christoph Hellwig
2009-07-07  7:40   ` Kevin Wolf
2009-07-07 10:28     ` Christoph Hellwig [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=20090707102847.GA23964@lst.de \
    --to=hch@lst.de \
    --cc=kwolf@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 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.