[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v7 05/12] migration: Make ram_save_target_page() a pointer
From: |
Juan Quintela |
Subject: |
Re: [PATCH v7 05/12] migration: Make ram_save_target_page() a pointer |
Date: |
Mon, 22 Aug 2022 23:35:27 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/28.1 (gnu/linux) |
Leonardo Bras Soares Passos <leobras@redhat.com> wrote:
> On Fri, Aug 19, 2022 at 6:52 AM Juan Quintela <quintela@redhat.com> wrote:
>>
>> - the value that we receive in ram_save_setup() is a RAMState
>> - We would have to change all the callers form
>> * ram_save_iterate()
>> * ram_find_and_save_block()
>> * ram_save_host_page()
>
> Maybe RAMState could be part of a bigger struct, and we could use
> something like a container_of().
> So whenever you want to use it, it would be available.
>
> What about that?
New struct it is:
typedef struct {
int (*ram_save_target_page)(RAMState *rs, PageSearchStatus *pss);
} MigrationOps;
And go from there.
Later, Juan.
- [PATCH v7 08/12] multifd: Add capability to enable/disable zero_page, (continued)
[PATCH v7 06/12] multifd: Make flags field thread local, Juan Quintela, 2022/08/02
[PATCH v7 10/12] multifd: Support for zero pages transmission, Juan Quintela, 2022/08/02
[PATCH v7 09/12] migration: Export ram_release_page(), Juan Quintela, 2022/08/02
[PATCH v7 11/12] multifd: Zero pages transmission, Juan Quintela, 2022/08/02
[PATCH v7 12/12] So we use multifd to transmit zero pages., Juan Quintela, 2022/08/02