From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37912) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b0Srg-0004fq-L0 for qemu-devel@nongnu.org; Wed, 11 May 2016 08:03:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b0Sre-0005wz-EE for qemu-devel@nongnu.org; Wed, 11 May 2016 08:03:43 -0400 Date: Wed, 11 May 2016 14:03:34 +0200 From: Kevin Wolf Message-ID: <20160511120334.GE4524@noname.str.redhat.com> References: <1462934735-12047-1-git-send-email-famz@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1462934735-12047-1-git-send-email-famz@redhat.com> Subject: Re: [Qemu-devel] [PATCH v2 0/3] block: More complete inactivate/invalidate of graph nodes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Fam Zheng Cc: qemu-devel@nongnu.org, Max Reitz , Stefan Hajnoczi , Alberto Garcia , qemu-block@nongnu.org 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