qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: Supriya Kannery <supriyak@linux.vnet.ibm.com>,
	Michael Tokarev <mjt@tls.msk.ru>,
	qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [V5 Patch 3/4]Qemu: Command "block_set" for dynamic block params change
Date: Thu, 28 Jul 2011 15:23:36 +0200	[thread overview]
Message-ID: <4E3162D8.9080702@redhat.com> (raw)
In-Reply-To: <CAJSP0QWeBpUDWcdaPW0_ARROWRaG31qCu-EqXMV1zO3ETnLD9Q@mail.gmail.com>

Am 28.07.2011 15:10, schrieb Stefan Hajnoczi:
> On Thu, Jul 28, 2011 at 11:23 AM, Kevin Wolf <kwolf@redhat.com> wrote:
>> Am 27.07.2011 16:51, schrieb Stefan Hajnoczi:
>>> I'll think about this some more, there are a couple of solutions like
>>> keeping only the file descriptor around, introducing a flush command
>>> that makes sure the file is in a clean state, or changing QED to not
>>> do this.
>>
>> Changing the format drivers doesn't really look like the right solution.
>>
>> Keeping the fd around looks okay, we can probably achieve this by
>> introducing a bdrv_reopen function. It means that we may need to reopen
>> the format layer, but it can't really fail.
> 
> My concern is that this assumes a single file descriptor.  For vmdk
> there may be multiple split files.
> 
> I'm almost starting to think bdrv_reopen() should be recursive down
> the BlockDriverState tree.

Yes, VMDK would have to call bdrv_reopen() for each file that it uses.

Kevin

  reply	other threads:[~2011-07-28 13:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 11:30 [Qemu-devel] [V5 Patch 0/4]Qemu: Set host cache from cmdline and monitor Supriya Kannery
2011-07-27 11:30 ` [Qemu-devel] [V5 Patch 1/4]Qemu: Enhance "info block" to display host cache setting Supriya Kannery
2011-07-27 14:19   ` Stefan Hajnoczi
2011-07-28 10:39     ` Supriya Kannery
2011-07-27 11:30 ` [Qemu-devel] [V5 Patch 2/4]Qemu: qerrors for file reopen, data sync and cmd syntax Supriya Kannery
2011-07-27 11:30 ` [Qemu-devel] [V5 Patch 3/4]Qemu: Command "block_set" for dynamic block params change Supriya Kannery
2011-07-27 12:58   ` Anthony Liguori
2011-07-27 14:31     ` Stefan Hajnoczi
2011-07-27 16:02       ` Anthony Liguori
2011-07-28  9:29         ` Stefan Hajnoczi
2011-08-01 15:22           ` Stefan Hajnoczi
2011-08-01 15:28             ` Anthony Liguori
2011-08-01 15:34               ` Stefan Hajnoczi
2011-08-01 15:44               ` Kevin Wolf
2011-08-01 15:44                 ` Anthony Liguori
2011-08-04  8:32                   ` Supriya Kannery
2011-08-04  8:31                     ` Stefan Hajnoczi
2011-08-04  9:33                       ` Supriya Kannery
2011-08-04  9:17                     ` Supriya Kannery
2011-08-01 15:44                 ` Stefan Hajnoczi
2011-08-01 15:46                   ` Anthony Liguori
2011-07-28 10:13         ` Supriya Kannery
2011-07-28 12:48           ` Anthony Liguori
2011-07-27 13:43   ` Michael Tokarev
2011-07-27 13:52     ` Anthony Liguori
2011-07-27 14:51     ` Stefan Hajnoczi
2011-07-28 10:23       ` Kevin Wolf
2011-07-28 13:10         ` Stefan Hajnoczi
2011-07-28 13:23           ` Kevin Wolf [this message]
2011-07-27 11:31 ` [Qemu-devel] [V5 Patch 4/4]Qemu: Add commandline -drive option 'hostcache' Supriya Kannery

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=4E3162D8.9080702@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hch@lst.de \
    --cc=mjt@tls.msk.ru \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    --cc=supriyak@linux.vnet.ibm.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).