From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>, Juan Quintela <quintela@redhat.com>,
Leonardo Bras <leobras@redhat.com>
Subject: [PULL 0/8] Migration 20230428 patches
Date: Wed, 3 May 2023 11:25:58 +0200 [thread overview]
Message-ID: <20230503092606.9415-1-quintela@redhat.com> (raw)
The following changes since commit 4ebc33f3f3b656ebf62112daca6aa0f8019b4891:
Merge tag 'pull-tcg-20230502-2' of https://gitlab.com/rth7680/qemu into staging (2023-05-02 21:18:45 +0100)
are available in the Git repository at:
https://gitlab.com/juan.quintela/qemu.git tags/migration-20230428-pull-request
for you to fetch changes up to 0deb7e9b6cfdb39d89a629e705d6176c511fa83e:
migration: Drop unused parameter for migration_tls_client_create() (2023-05-03 11:24:20 +0200)
----------------------------------------------------------------
Migraiton Pull request (20230428 take 2)
Hi
Dropped the compression cleanups to see if we find what is going on.
Please apply.
Later, Juan.
----------------------------------------------------------------
Juan Quintela (8):
multifd: We already account for this packet on the multifd thread
migration: Move ram_stats to its own file migration-stats.[ch]
migration: Rename ram_counters to mig_stats
migration: Rename RAMStats to MigrationAtomicStats
migration/rdma: Split the zero page case from acct_update_position
migration/rdma: Unfold last user of acct_update_position()
migration: Drop unused parameter for migration_tls_get_creds()
migration: Drop unused parameter for migration_tls_client_create()
migration/meson.build | 1 +
migration/migration-stats.c | 17 +++++++++++
migration/migration-stats.h | 41 +++++++++++++++++++++++++
migration/migration.c | 33 ++++++++++----------
migration/multifd.c | 12 ++++----
migration/postcopy-ram.c | 2 +-
migration/ram.c | 60 ++++++++++++++-----------------------
migration/ram.h | 24 ---------------
migration/rdma.c | 9 ++++--
migration/savevm.c | 3 +-
migration/tls.c | 15 ++++------
migration/tls.h | 3 +-
12 files changed, 120 insertions(+), 100 deletions(-)
create mode 100644 migration/migration-stats.c
create mode 100644 migration/migration-stats.h
--
2.40.0
next reply other threads:[~2023-05-03 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-03 9:25 Juan Quintela [this message]
2023-05-03 9:25 ` [PULL 1/8] multifd: We already account for this packet on the multifd thread Juan Quintela
2023-05-03 9:26 ` [PULL 2/8] migration: Move ram_stats to its own file migration-stats.[ch] Juan Quintela
2023-05-03 9:26 ` [PULL 3/8] migration: Rename ram_counters to mig_stats Juan Quintela
2023-05-03 9:26 ` [PULL 4/8] migration: Rename RAMStats to MigrationAtomicStats Juan Quintela
2023-05-03 9:26 ` [PULL 5/8] migration/rdma: Split the zero page case from acct_update_position Juan Quintela
2023-05-03 9:26 ` [PULL 6/8] migration/rdma: Unfold last user of acct_update_position() Juan Quintela
2023-05-03 9:26 ` [PULL 7/8] migration: Drop unused parameter for migration_tls_get_creds() Juan Quintela
2023-05-03 9:26 ` [PULL 8/8] migration: Drop unused parameter for migration_tls_client_create() Juan Quintela
2023-05-03 14:57 ` [PULL 0/8] Migration 20230428 patches 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=20230503092606.9415-1-quintela@redhat.com \
--to=quintela@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).