qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com.cn>, qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Fam Zheng <famz@redhat.com>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to track dirty sector
Date: Mon, 09 Mar 2015 08:38:25 +0100	[thread overview]
Message-ID: <54FD4DF1.5060805@redhat.com> (raw)
In-Reply-To: <201503091502590266464@sangfor.com.cn>



On 09/03/2015 08:03, Zhang Haoyu wrote:
> 
> On 2015-03-03 18:00:09, Paolo Bonzini wrote:
>>
>> On 03/03/2015 07:52, Zhang Haoyu wrote:
>>> Hi,
>>> If introducing bitmap to bdrv_commit to track dirty sector,
>>> could we implement guest non-disruption while performing commit?
>>
>> That is already implemented.  It uses the same code that implements
>> storage migration (block/mirror.c).
>>
> Hi Paolo,
> do you mean commit_active_start()?

Yes.

Paolo

  reply	other threads:[~2015-03-09  7:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  6:52 [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to track dirty sector Zhang Haoyu
2015-03-03  9:59 ` Paolo Bonzini
2015-03-09  7:03   ` Zhang Haoyu
2015-03-09  7:38     ` Paolo Bonzini [this message]
2015-03-09  8:14     ` Zhang Haoyu
2015-03-10  0:28       ` Fam Zheng
2015-03-10  1:30       ` [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to trackdirty sector Zhang Haoyu
2015-03-10  1:54         ` Fam Zheng
2015-03-10  2:12         ` [Qemu-devel] [RFC] introduce bitmap to bdrv_commit to trackdirtysector Zhang Haoyu
2015-03-10  2:58           ` Fam Zheng
2015-03-10  3:12           ` [Qemu-devel] [RFC] introduce bitmap to bdrv_commit totrackdirtysector Zhang Haoyu

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=54FD4DF1.5060805@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=famz@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mtosatti@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=zhanghy@sangfor.com.cn \
    /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).