From: Fam Zheng <famz@redhat.com>
To: Brian Steffens <briansteffens@gmail.com>,
Stefan Hajnoczi <stefanha@gmail.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/1] block: add block device shared field
Date: Wed, 6 Sep 2017 13:58:05 +0800 [thread overview]
Message-ID: <20170906055804.GA26413@lemon.lan> (raw)
In-Reply-To: <20170905095610.GF17449@stefanha-x1.localdomain>
On Tue, 09/05 10:56, Stefan Hajnoczi wrote:
> On Fri, Sep 01, 2017 at 08:10:54PM +0000, Brian Steffens wrote:
> > This adds a boolean option called 'shared' to block devices. It defaults
> > to off/false. When enabled for a particular block device, the 'shared' option
> > causes the block migration code to skip over syncing of that device. This
> > allows controlling exactly which block devices get synced during a migration.
> >
> > Signed-off-by: Brian Steffens <briansteffens@gmail.com>
> > ---
> > block.c | 7 +++++++
> > block/qapi.c | 2 ++
> > include/block/block.h | 1 +
> > include/block/block_int.h | 3 +++
> > migration/block.c | 4 ++++
> > qapi/block-core.json | 2 +-
> > 6 files changed, 18 insertions(+), 1 deletion(-)
>
> Thanks for the patch! Please email the relevant maintainers:
>
> $ scripts/get_maintainer.pl -f block.c
> Kevin Wolf <kwolf@redhat.com> (supporter:Block layer core)
> Max Reitz <mreitz@redhat.com> (supporter:Block layer core)
> qemu-block@nongnu.org (open list:Block layer core)
> qemu-devel@nongnu.org (open list:All patches CC here)
>
> I have CCed them so they see this email.
>
> > diff --git a/migration/block.c b/migration/block.c
> > index 9171f60028..b347c3dc61 100644
> > --- a/migration/block.c
> > +++ b/migration/block.c
> > @@ -402,6 +402,10 @@ static int init_blk_migration(QEMUFile *f)
> > bmds_bs = g_malloc0(num_bs * sizeof(*bmds_bs));
> >
> > for (i = 0, bs = bdrv_first(&it); bs; bs = bdrv_next(&it), i++) {
> > + if (bs->shared) {
If we go with this approach, I'd prefer a more specific name like
bs->skip_block_migration; "shared" has a lot meanings so is less readable.
Fam
> > + continue;
> > + }
> > +
prev parent reply other threads:[~2017-09-06 5:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 20:10 [Qemu-devel] [PATCH 1/1] block: add block device shared field Brian Steffens
2017-09-01 20:21 ` Eric Blake
2017-09-05 9:56 ` Stefan Hajnoczi
2017-09-05 15:10 ` Brian Steffens
2017-09-06 14:16 ` Stefan Hajnoczi
2017-09-06 5:58 ` Fam Zheng [this message]
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=20170906055804.GA26413@lemon.lan \
--to=famz@redhat.com \
--cc=briansteffens@gmail.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).