qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: John Snow <jsnow@redhat.com>, Juan Quintela <quintela@redhat.com>,
	Cleber Rosa <crosa@redhat.com>, Peter Xu <peterx@redhat.com>,
	Leonardo Bras <leobras@redhat.com>
Subject: [PULL 0/7] Migration 20230426 patches
Date: Thu, 27 Apr 2023 10:25:50 +0200	[thread overview]
Message-ID: <20230427082557.20994-1-quintela@redhat.com> (raw)

The following changes since commit c3f9aa8e488db330197c9217e38555f6772e8f07:

  Merge tag 'pull-qapi-2023-04-26' of https://repo.or.cz/qemu/armbru into staging (2023-04-26 07:23:32 +0100)

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 a67cceb071b76cc1631c67c11c845ffc4aa0803e:

  vmstate-static-checker: Recognize "num" field (2023-04-27 10:18:26 +0200)

----------------------------------------------------------------
Migration Pull request (take2)

With respect to the last PULL request:
- fix compilation on hosts without userfaultd.

Please, apply.

----------------------------------------------------------------

Juan Quintela (3):
  MAINTAINERS: Add Leonardo and Peter as reviewers
  migration: Move migrate_use_tls() to options.c
  migration: Move qmp_migrate_set_parameters() to options.c

Leonardo Bras (1):
  migration: Disable postcopy + multifd migration

Peter Xu (3):
  migration: Allow postcopy_ram_supported_by_host() to report err
  migration/vmstate-dump: Dump array size too as "num"
  vmstate-static-checker: Recognize "num" field

 MAINTAINERS                       |   2 +
 migration/migration.c             | 429 -----------------------------
 migration/migration.h             |   2 -
 migration/options.c               | 442 +++++++++++++++++++++++++++++-
 migration/options.h               |  12 +
 migration/postcopy-ram.c          |  60 ++--
 migration/postcopy-ram.h          |   3 +-
 migration/savevm.c                |   6 +-
 migration/tls.c                   |   3 +-
 scripts/vmstate-static-checker.py |  13 +-
 10 files changed, 501 insertions(+), 471 deletions(-)

-- 
2.40.0



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

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