From: Eric Blake <eblake@redhat.com>
To: mahaocong <mahaocong_work@163.com>, qemu-block@nongnu.org
Cc: fam@euphon.net, kwolf@redhat.com,
mahaocong <mahaocong@didichuxing.com>,
qemu-devel@nongnu.org, mreitz@redhat.com, jsnow@redhat.com
Subject: Re: [Qemu-devel] [PATCH v1] add new function to copy dirty-bitmap
Date: Thu, 3 Jan 2019 14:23:24 -0600 [thread overview]
Message-ID: <aa8862b8-0352-0422-2f33-7166d0c13a73@redhat.com> (raw)
In-Reply-To: <20190102100113.24621-1-mahaocong_work@163.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On 1/2/19 4:01 AM, mahaocong wrote:
> From: mahaocong <mahaocong@didichuxing.com>
>
> This patch adds new function to copy the hbitmap from an exist dirty-bitmap to
> another. The destination bitmap should have the same size and granularity with
> the source bitmap, or the copy will fail.
Is there a client in mind for this new code? And how does it differ to
what you can already achieve by the combination of
bdrv_clear_dirty_bitmap/bdrv_merge_dirty_bitmap?
>
> Signed-off-by: mahaocong <mahaocong@didichuxing.com>
Typical S-o-b and git authorship uses a preferred legal name rather than
a single-word username (there have been exceptions made in the past, but
we try not to introduce more without good reason). You can also teach
git to spell your name in both native UTF-8 characters and a Latinized
form, if you prefer.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-03 20:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-02 10:01 [Qemu-devel] [PATCH v1] add new function to copy dirty-bitmap mahaocong
2019-01-03 20:23 ` Eric Blake [this message]
2019-01-30 22:12 ` John Snow
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=aa8862b8-0352-0422-2f33-7166d0c13a73@redhat.com \
--to=eblake@redhat.com \
--cc=fam@euphon.net \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=mahaocong@didichuxing.com \
--cc=mahaocong_work@163.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/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).