All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, qemu-block@nongnu.org
Cc: qemu-devel@nongnu.org, jsnow@redhat.com, armbru@redhat.com,
	mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH 2/5] block: Remove dirty bitmaps from bdrv_move_feature_fields()
Date: Mon, 14 Mar 2016 09:55:00 -0600	[thread overview]
Message-ID: <56E6DED4.7020800@redhat.com> (raw)
In-Reply-To: <1457970292-12291-3-git-send-email-kwolf@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1635 bytes --]

On 03/14/2016 09:44 AM, Kevin Wolf wrote:
> This patch changes dirty bitmaps from following a BlockBackend in graph
> changes to sticking with the node they were created at. For the full
> discussion, read the following mailing list thread:
> 
>   [Qemu-block] block: Dirty bitmaps and COR in bdrv_move_feature_fields()
>   https://lists.nongnu.org/archive/html/qemu-block/2016-02/msg00745.html
> 
> In summary, the justification for this change is:
[snip nice list]
> 
> At the end of the day it seems to be very clear that it was a mistake to
> include dirty bitmaps in bdrv_move_feature_fields(). The functionality
> of moving bitmaps and/or attaching them to a BlockBackend instead will
> probably be needed, but it should be done with a new explicit QMP
> command or option.
> 
> Signed-off-by: Kevin Wolf <kwolf@redhat.com>
> ---
>  block.c | 3 ---
>  1 file changed, 3 deletions(-)

Reviewed-by: Eric Blake <eblake@redhat.com>

[Always interesting when a patch is way shorter than the justification
for why we need the patch]

> 
> diff --git a/block.c b/block.c
> index a75c4b3..698e2c7 100644
> --- a/block.c
> +++ b/block.c
> @@ -2284,9 +2284,6 @@ static void bdrv_move_feature_fields(BlockDriverState *bs_dest,
>  
>      /* dev info */
>      bs_dest->enable_write_cache = bs_src->enable_write_cache;
> -
> -    /* dirty bitmap */
> -    bs_dest->dirty_bitmaps      = bs_src->dirty_bitmaps;
>  }
>  
>  static void change_parent_backing_link(BlockDriverState *from,
> 

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]

  reply	other threads:[~2016-03-14 15:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-14 15:44 [Qemu-devel] [PATCH 0/5] block: API changes for 2.6 Kevin Wolf
2016-03-14 15:44 ` [Qemu-devel] [PATCH 1/5] block: Remove copy-on-read from bdrv_move_feature_fields() Kevin Wolf
2016-03-14 15:51   ` Eric Blake
2016-03-14 15:44 ` [Qemu-devel] [PATCH 2/5] block: Remove dirty bitmaps " Kevin Wolf
2016-03-14 15:55   ` Eric Blake [this message]
2016-03-14 15:44 ` [Qemu-devel] [PATCH 3/5] block: Remove cache.writeback from blockdev-add Kevin Wolf
2016-03-14 16:10   ` Eric Blake
2016-03-14 16:22     ` Kevin Wolf
2016-03-14 15:44 ` [Qemu-devel] [PATCH 4/5] block: Make backing files always writeback Kevin Wolf
2016-03-14 16:46   ` Eric Blake
2016-03-14 15:44 ` [Qemu-devel] [PATCH 5/5] block: Reject writethrough mode except at the root Kevin Wolf
2016-03-14 16:50   ` Eric Blake
2016-03-18 17:10 ` [Qemu-devel] [PATCH 0/5] block: API changes for 2.6 Kevin Wolf

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=56E6DED4.7020800@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.