qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, Max Reitz <mreitz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Alberto Garcia <berto@igalia.com>,
	qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 0/3] block: More complete inactivate/invalidate of graph nodes
Date: Wed, 11 May 2016 14:03:34 +0200	[thread overview]
Message-ID: <20160511120334.GE4524@noname.str.redhat.com> (raw)
In-Reply-To: <1462934735-12047-1-git-send-email-famz@redhat.com>

Am 11.05.2016 um 04:45 hat Fam Zheng geschrieben:
> v2: Two passes inactivation. [Kevin]
> 
> For now we only consider bs->file chain. In fact this is incomplete. For
> example, if qcow2 is a quorum child, we don't properly invalidate or inactivate
> it.  This series recurses into the subtrees in both bdrv_invalidate_cache_all
> and bdrv_inactivate_all. This is also necessary to make the image locking
> cooperate with migration.

Thanks, applied to block-next.

Kevin

      parent reply	other threads:[~2016-05-11 12:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-11  2:45 [Qemu-devel] [PATCH v2 0/3] block: More complete inactivate/invalidate of graph nodes Fam Zheng
2016-05-11  2:45 ` [Qemu-devel] [PATCH v2 1/3] block: Invalidate all children Fam Zheng
2016-05-11 10:37   ` Alberto Garcia
2016-05-11  2:45 ` [Qemu-devel] [PATCH v2 2/3] block: Drop superfluous invalidating bs->file from drivers Fam Zheng
2016-05-11 10:43   ` Alberto Garcia
2016-05-11  2:45 ` [Qemu-devel] [PATCH v2 3/3] block: Inactivate all children Fam Zheng
2016-05-11 12:03 ` Kevin Wolf [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=20160511120334.GE4524@noname.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=berto@igalia.com \
    --cc=famz@redhat.com \
    --cc=mreitz@redhat.com \
    --cc=qemu-block@nongnu.org \
    --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).