qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Yanan Wang" <wangyanan55@huawei.com>,
	"Juan Quintela" <quintela@redhat.com>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PULL 0/5] Migration 20230412 patches
Date: Wed, 12 Apr 2023 23:45:02 +0200	[thread overview]
Message-ID: <20230412214507.19816-1-quintela@redhat.com> (raw)

The following changes since commit abb02ce0e76a8e00026699a863ab2d11d88f56d4:

  Merge tag 'for-upstream' of https://repo.or.cz/qemu/kevin into staging (2023-04-11 16:19:06 +0100)

are available in the Git repository at:

  https://gitlab.com/juan.quintela/qemu.git tags/migration-20230412-pull-request

for you to fetch changes up to 28ef5339c37f1f78c2fa4df2295bc0cd73a0abfd:

  migration: fix ram_state_pending_exact() (2023-04-12 22:47:50 +0200)

----------------------------------------------------------------
Migration Pull request for 8.0

Last patches found:
- peter xu preempt channel fixes.
  needed for backward compatibility with old machine types.
- lukas fix to get compress working again.

- fix ram on s390x.  Get back to the old code, even when it shouldn't
  be needed, but as it fails on s390x, just revert.

Later, Juan.

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

Juan Quintela (1):
  migration: fix ram_state_pending_exact()

Lukas Straub (1):
  migration/ram.c: Fix migration with compress enabled

Peter Xu (3):
  io: tls: Inherit QIO_CHANNEL_FEATURE_SHUTDOWN on server side
  migration: Fix potential race on postcopy_qemufile_src
  migration: Recover behavior of preempt channel creation for pre-7.2

 migration/migration.h    | 41 +++++++++++++++++++++++++++++++++++++++-
 hw/core/machine.c        |  1 +
 io/channel-tls.c         |  3 +++
 migration/migration.c    | 19 +++++++++++++++++--
 migration/postcopy-ram.c | 30 ++++++++++++++++++++++-------
 migration/ram.c          | 27 +++++++++++++-------------
 6 files changed, 97 insertions(+), 24 deletions(-)

-- 
2.39.2



             reply	other threads:[~2023-04-12 21:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-12 21:45 Juan Quintela [this message]
2023-04-12 21:45 ` [PULL 1/5] io: tls: Inherit QIO_CHANNEL_FEATURE_SHUTDOWN on server side Juan Quintela
2023-04-12 21:45 ` [PULL 2/5] migration: Fix potential race on postcopy_qemufile_src Juan Quintela
2023-04-12 21:45 ` [PULL 3/5] migration: Recover behavior of preempt channel creation for pre-7.2 Juan Quintela
2023-04-12 21:45 ` [PULL 4/5] migration/ram.c: Fix migration with compress enabled Juan Quintela
2023-04-12 21:45 ` [PULL 5/5] migration: fix ram_state_pending_exact() Juan Quintela
2023-04-13 13:02 ` [PULL 0/5] Migration 20230412 patches Peter Maydell

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=20230412214507.19816-1-quintela@redhat.com \
    --to=quintela@redhat.com \
    --cc=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=wangyanan55@huawei.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).