From: Fabiano Rosas <farosas@suse.de>
To: Prasad Pandit <ppandit@redhat.com>
Cc: qemu-devel@nongnu.org, peterx@redhat.com, berrange@redhat.com,
Prasad Pandit <pjp@fedoraproject.org>
Subject: Re: [PATCH v4 4/4] tests/qtest/migration: add postcopy tests with multifd
Date: Tue, 28 Jan 2025 10:50:03 -0300 [thread overview]
Message-ID: <871pwnujxw.fsf@suse.de> (raw)
In-Reply-To: <CAE8KmOzCwr_vMYEGXR9RgAHb_hFp+wRznOhp+xxtDMGxaa7eGQ@mail.gmail.com>
Prasad Pandit <ppandit@redhat.com> writes:
> On Tue, 28 Jan 2025 at 11:00, Prasad Pandit <ppandit@redhat.com> wrote:
>> > for (int i = 0; i < MIGRATION_CAPABILITY__MAX; i++) {
>> > if (args->caps[i]) {
>> > migrate_set_capability(from, MigrationCapability_str(args->caps[i]), true);
>> > migrate_set_capability(to, MigrationCapability_str(args->caps[i]), true);
>> > }
>> > }
>> >
>> > We could also set the number of channels as a default value. The tests
>> > could overwrite it from the hook if needed.
>>
>> * Yes, this seems like a better option, I'll give it a try.
>
> Please see -> https://notebin.de/?317b9fc90a9a910d#dGKqq4r5pyMYU5SXYLFhd8wrzKRCxCcokTkTRBCUK7w
>
> @Fabiano: does this look okay? If it is, I'll further remove
> corresponding boolean fields from MigrateCommon struct etc.
You could include qapi-types-migration.h and use the actual enum, that
avoids the burden of having to keep the tests in sync with the code.
(I don't think keeping the caps in sync with the current-version tests
would break the compat tests, but please consider that as well)
And a generic helper that calls migrate_set_capability() for any
capabilites set. That solves the capabilities issue for all tests. We
can then move some default parameters setting into that function and
that should already reduce the number of hooks needed.
You can include it in this series or send a separate one, whatever is
easier for you. But we need to base this one on top of it eventually, I
would just send everything at once.
>
> Thank you.
> ---
> - Prasad
next prev parent reply other threads:[~2025-01-28 13:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-27 12:08 [PATCH v4 0/4] Allow to enable multifd and postcopy migration together Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 1/4] migration/multifd: move macros to multifd header Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 2/4] migration: refactor ram_save_target_page functions Prasad Pandit
2025-01-27 18:46 ` Fabiano Rosas
2025-01-27 12:08 ` [PATCH v4 3/4] migration: enable multifd and postcopy together Prasad Pandit
2025-01-27 12:08 ` [PATCH v4 4/4] tests/qtest/migration: add postcopy tests with multifd Prasad Pandit
2025-01-27 21:13 ` Fabiano Rosas
2025-01-28 5:30 ` Prasad Pandit
2025-01-28 11:17 ` Prasad Pandit
2025-01-28 13:50 ` Fabiano Rosas [this message]
2025-01-28 16:45 ` Prasad Pandit
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=871pwnujxw.fsf@suse.de \
--to=farosas@suse.de \
--cc=berrange@redhat.com \
--cc=peterx@redhat.com \
--cc=pjp@fedoraproject.org \
--cc=ppandit@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 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.