qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, "Peter Xu" <peterx@redhat.com>,
	"Steve Sistare" <steven.sistare@oracle.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH v5 0/6] migration: Test the new "file:" migration
Date: Wed, 04 Oct 2023 16:16:42 +0200	[thread overview]
Message-ID: <87jzs21nhx.fsf@secure.mitica> (raw)
In-Reply-To: <20230712190742.22294-1-farosas@suse.de> (Fabiano Rosas's message of "Wed, 12 Jul 2023 16:07:36 -0300")

Fabiano Rosas <farosas@suse.de> wrote:
> Based-on:
> [PATCH V4 0/2] migration file URI
> https://lore.kernel.org/r/1688135108-316997-1-git-send-email-steven.sistare@oracle.com

Full series are integrated for next PULL request.

Thanks, Juan.

>
> Since v4:
>
> - Implemented a separate version of test_precopy_common to be used
>   with the file transport (patch 6).
>
> v4:
> https://lore.kernel.org/r/20230706201927.15442-1-farosas@suse.de
>
> v3:
> https://lore.kernel.org/r/20230630212902.19925-1-farosas@suse.de
>
> v2:
> https://lore.kernel.org/r/20230628165542.17214-1-farosas@suse.de
>
> v1:
> https://lore.kernel.org/r/20230626182210.8792-1-farosas@suse.de
>
> Fabiano Rosas (6):
>   tests/qtest: migration: Expose migrate_set_capability
>   tests/qtest: migration: Add migrate_incoming_qmp helper
>   tests/qtest: migration: Use migrate_incoming_qmp where appropriate
>   migration: Set migration status early in incoming side
>   tests/qtest: migration: Add support for negative testing of
>     qmp_migrate
>   tests/qtest: migration-test: Add tests for file-based migration
>
>  migration/migration.c             |   7 +-
>  tests/qtest/libqtest.c            |  33 ++++++
>  tests/qtest/libqtest.h            |  28 +++++
>  tests/qtest/meson.build           |   1 +
>  tests/qtest/migration-helpers.c   |  60 ++++++++++
>  tests/qtest/migration-helpers.h   |  10 ++
>  tests/qtest/migration-test.c      | 185 ++++++++++++++++++++++++++----
>  tests/qtest/virtio-net-failover.c |  77 ++-----------
>  8 files changed, 308 insertions(+), 93 deletions(-)



      parent reply	other threads:[~2023-10-04 14:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 19:07 [PATCH v5 0/6] migration: Test the new "file:" migration Fabiano Rosas
2023-07-12 19:07 ` [PATCH v5 1/6] tests/qtest: migration: Expose migrate_set_capability Fabiano Rosas
2023-07-12 19:07 ` [PATCH v5 2/6] tests/qtest: migration: Add migrate_incoming_qmp helper Fabiano Rosas
2023-10-04 14:11   ` Juan Quintela
2023-07-12 19:07 ` [PATCH v5 3/6] tests/qtest: migration: Use migrate_incoming_qmp where appropriate Fabiano Rosas
2023-07-12 19:07 ` [PATCH v5 4/6] migration: Set migration status early in incoming side Fabiano Rosas
2023-10-04 14:12   ` Juan Quintela
2023-07-12 19:07 ` [PATCH v5 5/6] tests/qtest: migration: Add support for negative testing of qmp_migrate Fabiano Rosas
2023-07-12 19:07 ` [PATCH v5 6/6] tests/qtest: migration-test: Add tests for file-based migration Fabiano Rosas
2023-07-19 20:08   ` Peter Xu
2023-08-22 12:04 ` [PATCH v5 0/6] migration: Test the new "file:" migration Claudio Fontana
2023-10-04 14:16 ` Juan Quintela [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=87jzs21nhx.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=berrange@redhat.com \
    --cc=farosas@suse.de \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=steven.sistare@oracle.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).