From: "Richard W.M. Jones" <rjones@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: Ian Main <imain@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V9 0/2] Implement sync modes for drive-backup.
Date: Mon, 29 Jul 2013 11:03:48 +0100 [thread overview]
Message-ID: <20130729100348.GC1882@redhat.com> (raw)
In-Reply-To: <20130729093628.GA26806@T430s.redhat.com>
On Mon, Jul 29, 2013 at 05:36:28PM +0800, Fam Zheng wrote:
> On Mon, 07/29 10:02, Richard W.M. Jones wrote:
> > On Mon, Jul 29, 2013 at 10:52:44AM +0200, Kevin Wolf wrote:
> > > Am 26.07.2013 um 20:39 hat Ian Main geschrieben:
> > > > This patch adds sync modes on top of the work that Stefan Hajnoczi has done.
> > > >
> > > > These patches apply on kevin/block.
> > > >
> > > > Hopefully all is in order as this is my first QEMU patch. Many thanks to
> > > > Stephan and Fam Zheng for their help.
> > >
> > > Thanks, applied to the block branch (and meanwhile it's in master, too)
> >
> > I'd like to test this (the stuff in development, not the small bits
> > that are making their way into qemu), but I don't have a clear idea of
> > what are the latest patches and how they relate to each other, since
> > there are at least 2 people working on this, producing separate
> > patches asynchronously.
> >
> > What would be really helpful would be for one of the developers to put
> > up a qemu git tree that contains the latest stuff that needs to be
> > tested. github.com is an easy route to doing this.
> >
> > Rich.
> >
>
> Rich,
>
> If you mean image fleecing, you could possibly have a look at this (the
> latest)
>
> http://lists.nongnu.org/archive/html/qemu-devel/2013-07/msg05280.html
> [RFC PATCH 0/4] hmp/qmp: add snapshot option to nbd export
>
> The tree is here:
>
> git://github.com/famz/qemu.git nbd-snapshot
>
> BTW, the second latest one is:
>
> https://lists.gnu.org/archive/html/qemu-devel/2013-07/msg02719.html
> [PATCH v2 00/11] Point-in-time snapshot exporting over NBD
>
> The tree is:
>
> git://github.com/famz/qemu.git image-fleecing
>
> Neither are set final for the interface PoV, the second should be closer
> though.
Are there patches from Ian Main required on top of these to
finish off, or are those sufficient to test against?
Rich.
--
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming blog: http://rwmj.wordpress.com
Fedora now supports 80 OCaml packages (the OPEN alternative to F#)
next prev parent reply other threads:[~2013-07-29 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-26 18:39 [Qemu-devel] [PATCH V9 0/2] Implement sync modes for drive-backup Ian Main
2013-07-26 18:39 ` [Qemu-devel] [PATCH V9 1/2] " Ian Main
2013-07-26 18:39 ` [Qemu-devel] [PATCH V9 2/2] Add tests for sync modes 'TOP' and 'NONE' Ian Main
2013-07-29 8:52 ` [Qemu-devel] [PATCH V9 0/2] Implement sync modes for drive-backup Kevin Wolf
2013-07-29 9:02 ` Richard W.M. Jones
2013-07-29 9:36 ` Fam Zheng
2013-07-29 10:03 ` Richard W.M. Jones [this message]
2013-07-29 10:16 ` Fam Zheng
2013-07-29 10:54 ` Richard W.M. Jones
2013-07-30 16:47 ` Ian Main
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=20130729100348.GC1882@redhat.com \
--to=rjones@redhat.com \
--cc=famz@redhat.com \
--cc=imain@redhat.com \
--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).