From: Eric Blake <eblake@redhat.com>
To: Ma Haocong <mahaocong_work@163.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] qemu-img: add new function to remove bitmap in image
Date: Tue, 11 Sep 2018 09:08:34 -0500 [thread overview]
Message-ID: <a7a842bd-a2c3-c65c-f6a9-f16a1b97f9aa@redhat.com> (raw)
In-Reply-To: <3a26f63a-f05b-186f-316c-9a91be752065@redhat.com>
On 9/11/18 8:56 AM, Eric Blake wrote:
>> + bitmap = bdrv_find_dirty_bitmap(bs, bitmapname);
>> +
>> + /*
>> + * Dirty bitmap may not be load if the 'IN_USE' flag is set (e.g.
>> the
>> + * qemu thread is corrupted and the 'IN_USE' flag is not be
>> cleared),
>> + * so the result of bdrv_find_dirty_bitmap is null. In this case,
>> + * we delete bitmap in qcow2 file directly.
>> + */
>> + if (!bitmap) {
>> + bdrv_remove_persistent_dirty_bitmap(bs, bitmapname, &local_err);
>> + if (local_err != NULL) {
>> + ret = -1;
>> + goto out;
>> + }
>> + } else {
>> + if (bdrv_dirty_bitmap_get_persistance(bitmap)) {
>> + bdrv_remove_persistent_dirty_bitmap(bs, bitmapname,
>> &local_err);
>> + if (local_err != NULL) {
>> + ret = -1;
>> + goto out;
>> + }
>> + }
>> + bdrv_release_dirty_bitmap(bs, bitmap);
>> + }
>
> Why aren't you calling bdrv_block_dirty_bitmap_remove()? In general,
It helps if I ask my actual intended question: Why aren't you calling
qmp_block_dirty_bitmap_remove()?
> HMP commands that are mere wrappers around counterpart QMP commands are
> easier to maintain, rather than open-coding the same work in two places.
>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-09-11 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-11 8:37 [Qemu-devel] [PATCH v1 0/1] qemu-img: add new function to remove bitmap in image Ma Haocong
2018-09-11 8:37 ` [Qemu-devel] [PATCH v1 1/1] " Ma Haocong
2018-09-11 13:56 ` Eric Blake
2018-09-11 14:08 ` Eric Blake [this message]
2018-09-11 13:49 ` [Qemu-devel] [PATCH v1 0/1] " Eric Blake
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=a7a842bd-a2c3-c65c-f6a9-f16a1b97f9aa@redhat.com \
--to=eblake@redhat.com \
--cc=kwolf@redhat.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).