From: Fam Zheng <famz@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: Eric Blake <eblake@redhat.com>,
qemu-devel@nongnu.org, Andrea Arcangeli <aarcange@redhat.com>,
Juan Quintela <quintela@redhat.com>,
Alexey Perevalov <a.perevalov@samsung.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery
Date: Thu, 15 Mar 2018 17:04:26 +0800 [thread overview]
Message-ID: <20180315090426.GJ2733@lemon.usersys.redhat.com> (raw)
In-Reply-To: <20180315084132.GA2783@xz-mi>
On Thu, 03/15 16:41, Peter Xu wrote:
> On Thu, Mar 15, 2018 at 04:19:37PM +0800, Fam Zheng wrote:
> > On Mon, 03/12 12:45, Peter Xu wrote:
> > > On Fri, Mar 09, 2018 at 10:59:03AM -0600, Eric Blake wrote:
> > > > On 03/09/2018 10:54 AM, Eric Blake wrote:
> > > > > On 03/09/2018 03:15 AM, Peter Xu wrote:
> > > > > > Based-on: <20180309090006.10018-1-peterx@redhat.com>
> > > > > >
> > > > > > This series is based on the series:
> > > > > >
> > > > > > [PATCH v8 00/23] QMP: out-of-band (OOB) execution support
> > > > >
> > > > > Let's spell that in a way patchew understands:
> > > > >
> > > > > Based-on: <20180309090006.10018-1-peterx@redhat.com>
> > > > >
> > > >
> > > > Never mind - I missed that you snuck that in on the very first line (which
> > > > I'm used to overlooking because it's often a 'From:' author attribution,
> > > > instead of a patchew directive). I saw the patchew failure messages, but
> > > > didn't read them closely to see why it is failing, and merely assumed it was
> > > > because of the missing dependency...
> > >
> > > Yeh, but there still seems to be something wrong elsewhere since the
> > > series can pass compilation and docker tests on my host...
> > >
> > > Fam, what would happen if I firstly post OOB series, then postcopy
> > > series (which will have "based-on" on OOB series) right away? Could
> > > Patchew just ignore the "based-on" if I post the 2nd series too fast
> > > since Patchew may have not yet went through the first one?
> >
> > Could be. Git apply of the first one races with the appearance of the second one
> > in patchew's database. Or if the emails arrive in patchew's INBOX out-of-order,
> > the based-on tag will not work as expected.
>
> Thanks for confirming. Based-on is not frequently used, so I think
> what I need to do next time is I manually query and only send the 2nd
> series after patchew.org reported okay on the first one.
>
> It'll be good too if patchew can stop running tests if there is
> unknown based-on tag (either fully unknown, or work-in-progress), and
> report that "unknown tag found" message directly instead of test
> failures (since if there is a based-on, it's very possible that it'll
> fail).
>
> Further - I'm not sure whether serializing the work will be hard or
> not. Say, if series B has a based-on of A that is known but during
> processing, then postpone processing B until A finished. I won't ask
> for that though especially if it's not trivial.
Nice suggestions. Added to my TODO list now. Thanks,
Fam
prev parent reply other threads:[~2018-03-15 9:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 9:15 [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 01/23] migration: let incoming side use thread context Peter Xu
2018-03-12 17:27 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 02/23] migration: new postcopy-pause state Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 03/23] migration: implement "postcopy-pause" src logic Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 04/23] migration: allow dst vm pause on postcopy Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 05/23] migration: allow src return path to pause Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 06/23] migration: allow fault thread " Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 07/23] qmp: hmp: add migrate "resume" option Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 08/23] migration: rebuild channel on source Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 09/23] migration: new state "postcopy-recover" Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 10/23] migration: wakeup dst ram-load-thread for recover Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 11/23] migration: new cmd MIG_CMD_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 12/23] migration: new message MIG_RP_MSG_RECV_BITMAP Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 13/23] migration: new cmd MIG_CMD_POSTCOPY_RESUME Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 14/23] migration: new message MIG_RP_MSG_RESUME_ACK Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 15/23] migration: introduce SaveVMHandlers.resume_prepare Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 16/23] migration: synchronize dirty bitmap for resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 17/23] migration: setup ramstate " Peter Xu
2018-03-12 17:29 ` Dr. David Alan Gilbert
2018-03-12 17:30 ` Dr. David Alan Gilbert
2018-03-13 8:36 ` Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 18/23] migration: final handshake for the resume Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 19/23] migration: init dst in migration_object_init too Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 20/23] qmp/migration: new command migrate-recover Peter Xu
2018-03-12 17:33 ` Dr. David Alan Gilbert
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 21/23] hmp/migration: add migrate_recover command Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 22/23] migration/qmp: add command migrate-pause Peter Xu
2018-03-12 17:36 ` Dr. David Alan Gilbert
2018-03-13 8:54 ` Peter Xu
2018-03-09 9:15 ` [Qemu-devel] [PATCH v7 23/23] migration/hmp: add migrate_pause command Peter Xu
2018-03-09 9:47 ` [Qemu-devel] [PATCH v7 00/23] Migration: postcopy failure recovery no-reply
2018-03-09 9:48 ` no-reply
2018-03-09 9:49 ` no-reply
2018-03-09 9:51 ` no-reply
2018-03-09 9:56 ` no-reply
2018-03-09 9:57 ` no-reply
2018-03-09 16:54 ` Eric Blake
2018-03-09 16:59 ` Eric Blake
2018-03-12 4:45 ` Peter Xu
2018-03-15 8:19 ` Fam Zheng
2018-03-15 8:41 ` Peter Xu
2018-03-15 9:04 ` 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=20180315090426.GJ2733@lemon.usersys.redhat.com \
--to=famz@redhat.com \
--cc=a.perevalov@samsung.com \
--cc=aarcange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).