From: Liu Yuan <namei.unix@gmail.com>
To: Fam Zheng <famz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Benoit Canet <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [PATCH] block/quorum: implement .bdrv_co_get_block_status
Date: Fri, 18 Jul 2014 13:52:02 +0800 [thread overview]
Message-ID: <20140718055202.GG15811@ubuntu-trusty> (raw)
In-Reply-To: <20140718031131.GB2478@T430.redhat.com>
On Fri, Jul 18, 2014 at 11:11:31AM +0800, Fam Zheng wrote:
> On Thu, 07/17 19:50, Liu Yuan wrote:
> > - allow drive-mirror to create sprase mirror on images like qcow2
> > - allow qemu-img map to work as expected on quorum driver
> >
> > Cc: Benoit Canet <benoit@irqsave.net>
> > Cc: Kevin Wolf <kwolf@redhat.com>
> > Cc: Stefan Hajnoczi <stefanha@redhat.com>
> > Signed-off-by: Liu Yuan <namei.unix@gmail.com>
> > ---
> > block/quorum.c | 16 ++++++++++++++++
> > 1 file changed, 16 insertions(+)
> >
> > diff --git a/block/quorum.c b/block/quorum.c
> > index ebf5c71..f0d0a98 100644
> > --- a/block/quorum.c
> > +++ b/block/quorum.c
> > @@ -780,6 +780,21 @@ static coroutine_fn int quorum_co_flush(BlockDriverState *bs)
> > return result;
> > }
> >
> > +static int64_t coroutine_fn quorum_co_get_block_status(BlockDriverState *bs,
> > + int64_t sector_num,
> > + int nb_sectors,
> > + int *pnum)
> > +{
> > + BDRVQuorumState *s = bs->opaque;
> > + BlockDriverState *child_bs = s->bs[0];
>
> Should we consider other children?
>
No, other children are identical because we always do multiple sync writes
and at boot time we check the length.
Thanks
Yuan
next prev parent reply other threads:[~2014-07-18 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-17 11:50 [Qemu-devel] [PATCH] block/quorum: implement .bdrv_co_get_block_status Liu Yuan
2014-07-18 3:11 ` Fam Zheng
2014-07-18 5:52 ` Liu Yuan [this message]
2014-07-18 11:10 ` Kevin Wolf
2014-07-18 12:14 ` Eric Blake
2014-07-18 13:35 ` Paolo Bonzini
2014-07-21 3:01 ` Liu Yuan
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=20140718055202.GG15811@ubuntu-trusty \
--to=namei.unix@gmail.com \
--cc=benoit@irqsave.net \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.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).