qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: Amit Shah <amit.shah@redhat.com>,
	qemu-devel@nongnu.org, qemu-block@nongnu.org,
	Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] move qcow2_invalidate_cache() out of coroutine context
Date: Thu, 18 Feb 2016 15:54:28 +0100	[thread overview]
Message-ID: <56C5DB24.8060000@redhat.com> (raw)
In-Reply-To: <56C57ABC.5080207@openvz.org>



On 18/02/2016 09:03, Denis V. Lunev wrote:
> On 02/18/2016 08:17 AM, Amit Shah wrote:
>> Can someone from the block team please give this a review?
>
> Paolo, can you pls bless this? I think that the fix comes from the
> infrastructure layer and via your proposal.

Yes, I think it's fine from the block layer POV.  I proposed Denis this
fix after discussing the bug with Kevin.

Thanks Denis and Amit.

Paolo

  reply	other threads:[~2016-02-18 14:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-12  6:39 [Qemu-devel] [PATCH v2 0/2] move qcow2_invalidate_cache() out of coroutine context Denis V. Lunev
2016-02-12  6:39 ` [Qemu-devel] [PATCH 1/2] migration: move bdrv_invalidate_cache_all of " Denis V. Lunev
2016-02-23 12:54   ` Fam Zheng
2016-02-12  6:39 ` [Qemu-devel] [PATCH 2/2] " Denis V. Lunev
2016-02-12 12:50   ` Dr. David Alan Gilbert
2016-02-12 12:55     ` Paolo Bonzini
2016-02-12 16:25       ` Denis V. Lunev
2016-02-16  5:56 ` [Qemu-devel] [PATCH v2 0/2] move qcow2_invalidate_cache() out " Denis V. Lunev
2016-02-18  5:17 ` Amit Shah
2016-02-18  8:03   ` Denis V. Lunev
2016-02-18 14:54     ` Paolo Bonzini [this message]
2016-02-22  9:32       ` Amit Shah
2016-02-22  9:01   ` Denis V. Lunev
2016-02-23  7:39 ` Amit Shah
2016-02-23 10:47   ` Amit Shah
2016-02-23 12:39     ` Denis V. Lunev

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=56C5DB24.8060000@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=amit.shah@redhat.com \
    --cc=den@openvz.org \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=quintela@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).