All of lore.kernel.org
 help / color / mirror / Atom feed
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 v6 4/4] tests/qtest/migration: add postcopy tests with multifd
Date: Tue, 25 Feb 2025 10:07:17 -0300	[thread overview]
Message-ID: <875xkyyxyy.fsf@suse.de> (raw)
In-Reply-To: <CAE8KmOzNoMrpPjvTinVrcQ0VKbgFUyyRWWdHE02_HwU4dpjx=g@mail.gmail.com>

Prasad Pandit <ppandit@redhat.com> writes:

> Hello Fabiano,
>
> On Tue, 18 Feb 2025 at 19:58, Fabiano Rosas <farosas@suse.de> wrote:
>> >> > +static void test_multifd_postcopy_tcp_cancel(void)
>> >> > +{
>> >> > +    postcopy_ram = true;
>> >> > +    test_multifd_tcp_cancel();
>> >> > +    postcopy_ram = false;
>> >>
>> >> You could pass this in, there's just one other caller.
>>
>> To make postcopy_ram be passed in as an argument to
>> test_multifd_tcp_cancel(). Having globals tend to get in the way of
>> refactoring stuff later. We already had issues with tmpfs being global
>> all over the place.
>
> * This looks tricky to do. test_multifd_tcp_cancel() is called via
> migration_test_add(), which expects a function pointer of type => void
> (*fn)(void). Changing 'migration_test_add' signature would entail
> adding a parameter to all functions called by it.
>

Indeed. Leave it then. If I think of something I'll let you know.

> Thank you.
> ---
>   - Prasad


      reply	other threads:[~2025-02-25 13:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-15 12:31 [PATCH v6 0/4] Allow to enable multifd and postcopy migration together Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 1/4] migration/multifd: move macros to multifd header Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 2/4] migration: enable multifd and postcopy together Prasad Pandit
2025-02-17 21:49   ` Fabiano Rosas
2025-02-18  8:17     ` Prasad Pandit
2025-02-18 14:22       ` Fabiano Rosas
2025-02-19 11:57         ` Prasad Pandit
2025-02-19 17:22           ` Fabiano Rosas
2025-02-20  9:47             ` Prasad Pandit
2025-02-20 13:36               ` Fabiano Rosas
2025-02-21  8:44                 ` Prasad Pandit
2025-02-18 11:17   ` Juraj Marcin
2025-02-19  7:13     ` Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 3/4] tests/qtest/migration: consolidate set capabilities Prasad Pandit
2025-02-17 15:17   ` Fabiano Rosas
2025-02-18  8:53     ` Prasad Pandit
2025-02-15 12:31 ` [PATCH v6 4/4] tests/qtest/migration: add postcopy tests with multifd Prasad Pandit
2025-02-17 15:33   ` Fabiano Rosas
2025-02-18  8:58     ` Prasad Pandit
2025-02-18 14:28       ` Fabiano Rosas
2025-02-25  7:25         ` Prasad Pandit
2025-02-25 13:07           ` Fabiano Rosas [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=875xkyyxyy.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.