From: Richard Henderson <richard.henderson@linaro.org>
To: Juan Quintela <quintela@redhat.com>, qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>, Peter Xu <peterx@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: Re: [PULL 00/21] Migration 20230530 patches
Date: Tue, 30 May 2023 06:23:37 -0700 [thread overview]
Message-ID: <a0fa954e-9903-841d-9c00-c035a6ddc8db@linaro.org> (raw)
In-Reply-To: <20230530115429.1998-1-quintela@redhat.com>
On 5/30/23 04:54, Juan Quintela wrote:
> The following changes since commit aa9bbd865502ed517624ab6fe7d4b5d89ca95e43:
>
> Merge tag 'pull-ppc-20230528' ofhttps://gitlab.com/danielhb/qemu into staging (2023-05-29 14:31:52 -0700)
>
> are available in the Git repository at:
>
> https://gitlab.com/juan.quintela/qemu.git tags/migration-20230530-pull-request
>
> for you to fetch changes up to d83da4626ebc1462e8f0065d446f97aece681d90:
>
> migration/rdma: Check sooner if we are in postcopy for save_page() (2023-05-30 13:27:54 +0200)
>
> ----------------------------------------------------------------
> Migration 20230530 Pull request
>
> Hi
>
> On this PULL request:
>
> - Set vmstate migration failure right (vladimir)
> - Migration QEMUFileHook removal (juan)
> - Migration Atomic counters (juan)
>
> Please apply.
Fails immediately:
In file included from ../src/migration/ram.c:61:
../src/migration/rdma.h:52:5: error: no previous prototype for ‘rdma_registration_handle’
[-Werror=missing-prototypes]
52 | int rdma_registration_handle(QEMUFile *f) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~~
../src/migration/rdma.h:53:5: error: no previous prototype for ‘rdma_registration_start’
[-Werror=missing-prototypes]
53 | int rdma_registration_start(QEMUFile *f, uint64_t flags) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~
../src/migration/rdma.h:54:5: error: no previous prototype for ‘rdma_registration_stop’
[-Werror=missing-prototypes]
54 | int rdma_registration_stop(QEMUFile *f, uint64_t flags) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~
../src/migration/rdma.h:55:5: error: no previous prototype for
‘rdma_block_notification_handle’ [-Werror=missing-prototypes]
55 | int rdma_block_notification_handle(QEMUFile *f, const char *name) { return 0; }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
../src/migration/rdma.h:56:5: error: no previous prototype for ‘rdma_control_save_page’
[-Werror=missing-prototypes]
56 | int rdma_control_save_page(QEMUFile *f, ram_addr_t block_offset,
| ^~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
r~
next prev parent reply other threads:[~2023-05-30 13:23 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 11:54 [PULL 00/21] Migration 20230530 patches Juan Quintela
2023-05-30 11:54 ` [PULL 01/21] runstate: add runstate_get() Juan Quintela
2023-05-30 11:54 ` [PULL 02/21] migration: never fail in global_state_store() Juan Quintela
2023-05-30 11:54 ` [PULL 03/21] runstate: drop unused runstate_store() Juan Quintela
2023-05-30 11:54 ` [PULL 04/21] migration: switch from .vm_was_running to .vm_old_state Juan Quintela
2023-05-30 11:54 ` [PULL 05/21] migration: restore vmstate on migration failure Juan Quintela
2023-05-30 11:54 ` [PULL 06/21] migration: Don't abuse qemu_file transferred for RDMA Juan Quintela
2023-05-30 11:54 ` [PULL 07/21] migration/RDMA: It is accounting for zero/normal pages in two places Juan Quintela
2023-05-30 11:54 ` [PULL 08/21] migration/rdma: Remove QEMUFile parameter when not used Juan Quintela
2023-05-30 11:54 ` [PULL 09/21] migration/rdma: Don't use imaginary transfers Juan Quintela
2023-05-30 11:54 ` [PULL 10/21] migration: Remove unused qemu_file_credit_transfer() Juan Quintela
2023-05-30 11:54 ` [PULL 11/21] migration/rdma: Simplify the function that saves a page Juan Quintela
2023-05-30 11:54 ` [PULL 12/21] migration: Create migrate_rdma() Juan Quintela
2023-05-30 11:54 ` [PULL 13/21] migration/rdma: Unfold ram_control_before_iterate() Juan Quintela
2023-05-30 11:54 ` [PULL 14/21] migration/rdma: Unfold ram_control_after_iterate() Juan Quintela
2023-05-30 11:54 ` [PULL 15/21] migration/rdma: Remove all uses of RAM_CONTROL_HOOK Juan Quintela
2023-05-30 11:54 ` [PULL 16/21] migration/rdma: Unfold hook_ram_load() Juan Quintela
2023-05-30 11:54 ` [PULL 17/21] migration/rdma: Create rdma_control_save_page() Juan Quintela
2023-05-30 11:54 ` [PULL 18/21] qemu-file: Remove QEMUFileHooks Juan Quintela
2023-05-30 11:54 ` [PULL 19/21] migration/rdma: Move rdma constants from qemu-file.h to rdma.h Juan Quintela
2023-05-30 11:54 ` [PULL 20/21] migration/rdma: Remove qemu_ prefix from exported functions Juan Quintela
2023-05-30 11:54 ` [PULL 21/21] migration/rdma: Check sooner if we are in postcopy for save_page() Juan Quintela
2023-05-30 13:23 ` Richard Henderson [this message]
2023-05-30 14:47 ` [PULL 00/21] Migration 20230530 patches Juan Quintela
-- strict thread matches above, loose matches on Subject: below --
2023-05-30 18:25 Juan Quintela
2023-05-30 20:23 ` Richard Henderson
2023-05-31 7:28 ` Juan Quintela
2023-05-31 9:10 ` Juan Quintela
[not found] ` <87mt1ktdr8.fsf@secure.mitica>
2023-05-31 21:28 ` Richard Henderson
2023-06-01 6:47 ` Juan Quintela
2023-06-01 8:27 ` Daniel P. Berrangé
2023-06-01 9:05 ` Daniel P. Berrangé
2023-06-01 11:46 ` Juan Quintela
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=a0fa954e-9903-841d-9c00-c035a6ddc8db@linaro.org \
--to=richard.henderson@linaro.org \
--cc=leobras@redhat.com \
--cc=pbonzini@redhat.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 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).