qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: qemu-devel@nongnu.org,  Peter Xu <peterx@redhat.com>,
	 Cleber Rosa <crosa@redhat.com>,  John Snow <jsnow@redhat.com>,
	 Leonardo Bras <leobras@redhat.com>
Subject: Re: [PULL 0/7] Migration 20230426 patches
Date: Thu, 27 Apr 2023 10:19:31 +0200	[thread overview]
Message-ID: <87sfcld9f0.fsf@secure.mitica> (raw)
In-Reply-To: <5db4affa-d831-2ba1-7175-c5ba32182ef1@linaro.org> (Richard Henderson's message of "Thu, 27 Apr 2023 08:51:03 +0100")

Richard Henderson <richard.henderson@linaro.org> wrote:
> On 4/26/23 19:12, Juan Quintela wrote:
>> The following changes since commit 9c894df3a37d675652390f7dbbe2f65b7bad7efa:
>>    migration: Create migrate_max_bandwidth() function (2023-04-24
>> 15:01:47 +0200)
>> are available in the Git repository at:
>>    https://gitlab.com/juan.quintela/qemu.git
>> tags/migration-20230426-pull-request
>> for you to fetch changes up to
>> 7b5cd8ff519e9fe3df6cda65428a6f1aa28a6ced:
>>    vmstate-static-checker: Recognize "num" field (2023-04-26
>> 19:17:55 +0200)
>> ----------------------------------------------------------------
>> Migration Pull request
>> Hi
>> This PULL request is on top of migration-20230424 already queued by
>> Richard.
>> It contains:
>> - MAINTAINERS: make peter and leo reviewers for migration (juan)
>> - Disable postcopy + multifd together. It needs at least to call
>>    send_sync before it will work. (juan)
>> - Improve postcopy error messages (peter)
>> - vmstate checker: Compare sizes of arrays correctly (peter)
>> - Move more capability functions to options.c (juan)
>> Please, apply.
>
> Build failures:
>
> https://gitlab.com/qemu-project/qemu/-/jobs/4187732684#L2303

Fixed.

Sorry about that.
It only fails on hosts that don't support userfaultd() (i.e. non-linux).

Will resend.

Sorry for the noise.

Later, Juan.


>
> ../migration/postcopy-ram.c:1368:6: error: conflicting types for
> 'postcopy_ram_supported_by_host'; have '_Bool(MigrationIncomingState
> *)'
>  1368 | bool postcopy_ram_supported_by_host(MigrationIncomingState *mis)
>       |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> In file included from ../migration/migration.h:27,
>                  from ../migration/postcopy-ram.c:22:
> ../migration/postcopy-ram.h:17:6: note: previous declaration of
> 'postcopy_ram_supported_by_host' with type
> '_Bool(MigrationIncomingState *, Error **)'
>    17 | bool postcopy_ram_supported_by_host(MigrationIncomingState *mis,
>       |      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
> r~



  reply	other threads:[~2023-04-27  8:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 18:12 [PULL 0/7] Migration 20230426 patches Juan Quintela
2023-04-26 18:12 ` [PULL 1/7] migration: Disable postcopy + multifd migration Juan Quintela
2023-04-26 18:12 ` [PULL 2/7] MAINTAINERS: Add Leonardo and Peter as reviewers Juan Quintela
2023-04-26 18:12 ` [PULL 3/7] migration: Move migrate_use_tls() to options.c Juan Quintela
2023-04-26 18:12 ` [PULL 4/7] migration: Move qmp_migrate_set_parameters() " Juan Quintela
2023-04-26 18:12 ` [PULL 5/7] migration: Allow postcopy_ram_supported_by_host() to report err Juan Quintela
2023-04-26 18:12 ` [PULL 6/7] migration/vmstate-dump: Dump array size too as "num" Juan Quintela
2023-04-26 18:12 ` [PULL 7/7] vmstate-static-checker: Recognize "num" field Juan Quintela
2023-04-27  7:51 ` [PULL 0/7] Migration 20230426 patches Richard Henderson
2023-04-27  8:19   ` Juan Quintela [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-04-27  8:25 Juan Quintela
2023-04-27 13:26 ` Richard Henderson

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=87sfcld9f0.fsf@secure.mitica \
    --to=quintela@redhat.com \
    --cc=crosa@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=leobras@redhat.com \
    --cc=peterx@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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 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).