From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Xu <peterx@redhat.com>
Cc: qemu-devel@nongnu.org,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>,
Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
Manish Mishra <manish.mishra@nutanix.com>
Subject: Re: [PATCH v7 11/14] tests: Move MigrateCommon upper
Date: Wed, 25 May 2022 09:26:38 +0100 [thread overview]
Message-ID: <Yo3oPh1WHteJvhFE@redhat.com> (raw)
In-Reply-To: <20220524221151.18225-12-peterx@redhat.com>
On Tue, May 24, 2022 at 06:11:48PM -0400, Peter Xu wrote:
> So that it can be used in postcopy tests too soon.
>
> Signed-off-by: Peter Xu <peterx@redhat.com>
> ---
> tests/qtest/migration-test.c | 144 +++++++++++++++++------------------
> 1 file changed, 72 insertions(+), 72 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-05-25 8:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 22:11 [PATCH v7 00/14] migration: Postcopy Preemption Peter Xu
2022-05-24 22:11 ` [PATCH v7 01/14] migration: Add postcopy-preempt capability Peter Xu
2022-06-21 21:03 ` Juan Quintela
2022-05-24 22:11 ` [PATCH v7 02/14] migration: Postcopy preemption preparation on channel creation Peter Xu
2022-06-22 0:05 ` Juan Quintela
2022-05-24 22:11 ` [PATCH v7 03/14] migration: Postcopy preemption enablement Peter Xu
2022-05-24 22:11 ` [PATCH v7 04/14] migration: Postcopy recover with preempt enabled Peter Xu
2022-05-24 22:11 ` [PATCH v7 05/14] migration: Create the postcopy preempt channel asynchronously Peter Xu
2022-05-24 22:11 ` [PATCH v7 06/14] migration: Add property x-postcopy-preempt-break-huge Peter Xu
2022-05-24 22:11 ` [PATCH v7 07/14] migration: Add helpers to detect TLS capability Peter Xu
2022-05-24 22:11 ` [PATCH v7 08/14] migration: Export tls-[creds|hostname|authz] params to cmdline too Peter Xu
2022-05-24 22:11 ` [PATCH v7 09/14] migration: Enable TLS for preempt channel Peter Xu
2022-05-24 22:11 ` [PATCH v7 10/14] migration: Respect postcopy request order in preemption mode Peter Xu
2022-05-24 22:11 ` [PATCH v7 11/14] tests: Move MigrateCommon upper Peter Xu
2022-05-25 8:26 ` Daniel P. Berrangé [this message]
2022-05-24 22:11 ` [PATCH v7 12/14] tests: Add postcopy tls migration test Peter Xu
2022-05-24 22:11 ` [PATCH v7 13/14] tests: Add postcopy tls recovery " Peter Xu
2022-05-25 14:55 ` Dr. David Alan Gilbert
2022-05-24 22:11 ` [PATCH v7 14/14] tests: Add postcopy preempt tests Peter Xu
2022-06-08 16:26 ` Dr. David Alan Gilbert
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=Yo3oPh1WHteJvhFE@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=manish.mishra@nutanix.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.