From: "Zhang, Chen" <chen.zhang@intel.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: Zhanghailiang <zhang.zhanghailiang@huawei.com>,
qemu-dev <qemu-devel@nongnu.org>,
Zhang Chen <zhangckid@gmail.com>
Subject: RE: [PATCH V3 0/3] migration/colo: Optimize COLO framework code
Date: Mon, 22 Jun 2020 06:52:40 +0000 [thread overview]
Message-ID: <f02f06aa12cd406db9f681d11a2b3b47@intel.com> (raw)
In-Reply-To: <20200617122541.GD2776@work-vm>
> -----Original Message-----
> From: Dr. David Alan Gilbert <dgilbert@redhat.com>
> Sent: Wednesday, June 17, 2020 8:26 PM
> To: Zhang, Chen <chen.zhang@intel.com>
> Cc: qemu-dev <qemu-devel@nongnu.org>; Zhang Chen
> <zhangckid@gmail.com>; Zhanghailiang <zhang.zhanghailiang@huawei.com>
> Subject: Re: [PATCH V3 0/3] migration/colo: Optimize COLO framework code
>
> * Zhang, Chen (chen.zhang@intel.com) wrote:
> > Hi Dave,
> >
>
> I think it's OK; I guess Zhanghailiang is going to do a pull for it?
> One thought about the change of use of MIGRATION_STATUS_ACTIVE; I
> think it's OK at the moment - but the migration states and the way they
> change becomes part of the API - changing which states we use can confuse
> management applications; since there's no libvirt support, I'll leave it to
> Zhanghailiang to know if that's OK.
Hi Hailiang/Dave,
Current upstream libvirt can't support COLO, it looks no new issue for normal migration process.
For the future, new COLO migration status is good for COLO enable work on libvirt and upper layer.
Thanks
Zhang Chen
>
> Dave
>
>
> >
> > Thanks
> > Zhang Chen
> >
> > > -----Original Message-----
> > > From: Zhang, Chen <chen.zhang@intel.com>
> > > Sent: Monday, June 8, 2020 3:46 AM
> > > To: Dr . David Alan Gilbert <dgilbert@redhat.com>; qemu-dev <qemu-
> > > devel@nongnu.org>
> > > Cc: Zhang Chen <zhangckid@gmail.com>; Zhanghailiang
> > > <zhang.zhanghailiang@huawei.com>; Zhang, Chen
> <chen.zhang@intel.com>
> > > Subject: [PATCH V3 0/3] migration/colo: Optimize COLO framework code
> > >
> > > From: Zhang Chen <chen.zhang@intel.com>
> > >
> > > This series optimize some code of COLO, please review.
> > >
> > > Zhang Chen (3):
> > > migration/colo: Optimize COLO boot code path
> > > migration/colo: Update checkpoint time lately
> > > migration/migration.c: Remove MIGRATION_STATUS_ACTIVE in
> > > migration_iteration_finish
> > >
> > > migration/colo.c | 7 ++-----
> > > migration/migration.c | 12 +++++-------
> > > 2 files changed, 7 insertions(+), 12 deletions(-)
> > >
> > > --
> > > 2.17.1
> >
> --
> Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2020-06-22 6:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 19:46 [PATCH V3 0/3] migration/colo: Optimize COLO framework code Zhang Chen
2020-06-07 19:46 ` [PATCH V3 1/3] migration/colo: Optimize COLO boot code path Zhang Chen
2020-06-08 7:24 ` Lukas Straub
2020-06-07 19:46 ` [PATCH V3 2/3] migration/colo: Update checkpoint time lately Zhang Chen
2020-06-07 19:46 ` [PATCH V3 3/3] migration/migration.c: Remove MIGRATION_STATUS_ACTIVE in migration_iteration_finish Zhang Chen
2020-06-08 7:25 ` Lukas Straub
2020-06-10 6:00 ` [PATCH V3 0/3] migration/colo: Optimize COLO framework code Zhang, Chen
2020-06-17 12:25 ` Dr. David Alan Gilbert
2020-06-22 6:52 ` Zhang, Chen [this message]
2020-07-08 6:39 ` Zhang, Chen
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=f02f06aa12cd406db9f681d11a2b3b47@intel.com \
--to=chen.zhang@intel.com \
--cc=dgilbert@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=zhang.zhanghailiang@huawei.com \
--cc=zhangckid@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).