From: Fabiano Rosas <farosas@suse.de>
To: qemu-devel@nongnu.org
Cc: Peter Xu <peterx@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>
Subject: [PULL 0/9] Migration patches for 2024-05-22
Date: Wed, 22 May 2024 19:20:25 -0300 [thread overview]
Message-ID: <20240522222034.4001-1-farosas@suse.de> (raw)
The following changes since commit 01782d6b294f95bcde334386f0aaac593cd28c0d:
Merge tag 'hw-misc-20240517' of https://github.com/philmd/qemu into staging (2024-05-18 11:49:01 +0200)
are available in the Git repository at:
https://gitlab.com/farosas/qemu.git tags/migration-20240522-pull-request
for you to fetch changes up to 8f023a0bd946bb0c122543c64fe2b34bad0dd048:
tests/qtest/migration-test: Fix the check for a successful run of analyze-migration.py (2024-05-22 17:34:41 -0300)
----------------------------------------------------------------
Migration pull request
- Li Zhijian's COLO minor fixes
- Marc-André's virtio-gpu fix
- Fiona's virtio-net USO fix
- A couple of migration-test fixes from Thomas
----------------------------------------------------------------
Fiona Ebner (1):
hw/core/machine: move compatibility flags for VirtIO-net USO to
machine 8.1
Li Zhijian (3):
migration/colo: Minor fix for colo error message
migration/colo: make colo_incoming_co() return void
migration/colo: Tidy up bql_unlock() around bdrv_activate_all()
Marc-André Lureau (3):
migration: add "exists" info to load-state-field trace
migration: fix a typo
virtio-gpu: fix v2 migration
Thomas Huth (2):
tests/qtest/migration-test: Run some basic tests on s390x and ppc64
with TCG, too
tests/qtest/migration-test: Fix the check for a successful run of
analyze-migration.py
hw/core/machine.c | 7 +++---
hw/display/virtio-gpu.c | 30 ++++++++++++++++++-------
include/hw/virtio/virtio-gpu.h | 1 +
include/migration/colo.h | 2 +-
migration/colo-stubs.c | 3 +--
migration/colo.c | 12 +++-------
migration/migration.c | 12 +++++-----
migration/trace-events | 2 +-
migration/vmstate.c | 7 +++---
tests/qtest/migration-test.c | 41 +++++++++++++++++-----------------
10 files changed, 64 insertions(+), 53 deletions(-)
--
2.35.3
next reply other threads:[~2024-05-22 22:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-22 22:20 Fabiano Rosas [this message]
2024-05-22 22:20 ` [PULL 1/9] migration/colo: Minor fix for colo error message Fabiano Rosas
2024-05-22 22:20 ` [PULL 2/9] migration/colo: make colo_incoming_co() return void Fabiano Rosas
2024-05-22 22:20 ` [PULL 3/9] migration/colo: Tidy up bql_unlock() around bdrv_activate_all() Fabiano Rosas
2024-05-22 22:20 ` [PULL 4/9] migration: add "exists" info to load-state-field trace Fabiano Rosas
2024-05-22 22:20 ` [PULL 5/9] migration: fix a typo Fabiano Rosas
2024-05-22 22:20 ` [PULL 6/9] virtio-gpu: fix v2 migration Fabiano Rosas
2024-05-29 10:50 ` Fiona Ebner
2024-05-29 13:26 ` Fabiano Rosas
2024-05-22 22:20 ` [PULL 7/9] hw/core/machine: move compatibility flags for VirtIO-net USO to machine 8.1 Fabiano Rosas
2024-05-22 22:20 ` [PULL 8/9] tests/qtest/migration-test: Run some basic tests on s390x and ppc64 with TCG, too Fabiano Rosas
2024-05-22 22:20 ` [PULL 9/9] tests/qtest/migration-test: Fix the check for a successful run of analyze-migration.py Fabiano Rosas
2024-05-23 2:02 ` [PULL 0/9] Migration patches for 2024-05-22 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=20240522222034.4001-1-farosas@suse.de \
--to=farosas@suse.de \
--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).