From: Stefan Hajnoczi <stefanha@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, Peter Xu <peterx@redhat.com>
Subject: Re: [PULL 00/25] Migration patches for 2025-01-10
Date: Sun, 12 Jan 2025 10:37:35 -0500 [thread overview]
Message-ID: <20250112153735.GA31245@fedora> (raw)
In-Reply-To: <20250110121413.12336-1-farosas@suse.de>
[-- Attachment #1: Type: text/plain, Size: 116 bytes --]
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/10.0 for any user-visible changes.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2025-01-12 15:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 12:13 [PULL 00/25] Migration patches for 2025-01-10 Fabiano Rosas
2025-01-10 12:13 ` [PULL 01/25] migration/multifd: Fix compile error caused by page_size usage Fabiano Rosas
2025-01-10 12:13 ` [PULL 02/25] migration/multifd: Further remove the SYNC on complete Fabiano Rosas
2025-01-10 12:13 ` [PULL 03/25] migration/multifd: Allow to sync with sender threads only Fabiano Rosas
2025-01-10 12:13 ` [PULL 04/25] migration/ram: Move RAM_SAVE_FLAG* into ram.h Fabiano Rosas
2025-01-10 12:13 ` [PULL 05/25] migration/multifd: Unify RAM_SAVE_FLAG_MULTIFD_FLUSH messages Fabiano Rosas
2025-01-10 12:13 ` [PULL 06/25] migration/multifd: Remove sync processing on postcopy Fabiano Rosas
2025-01-10 12:13 ` [PULL 07/25] migration/multifd: Cleanup src flushes on condition check Fabiano Rosas
2025-01-10 12:13 ` [PULL 08/25] migration/multifd: Document the reason to sync for save_setup() Fabiano Rosas
2025-01-10 12:13 ` [PULL 09/25] migration/multifd: Fix compat with QEMU < 9.0 Fabiano Rosas
2025-01-10 12:13 ` [PULL 10/25] migration: Add helper to get target runstate Fabiano Rosas
2025-01-10 12:13 ` [PULL 11/25] qmp/cont: Only activate disks if migration completed Fabiano Rosas
2025-01-10 12:14 ` [PULL 12/25] migration/block: Make late-block-active the default Fabiano Rosas
2025-01-10 12:14 ` [PULL 13/25] migration/block: Apply late-block-active behavior to postcopy Fabiano Rosas
2025-01-10 12:14 ` [PULL 14/25] migration/block: Fix possible race with block_inactive Fabiano Rosas
2025-01-10 12:14 ` [PULL 15/25] migration/block: Rewrite disk activation Fabiano Rosas
2025-01-10 12:14 ` [PULL 16/25] migration: Add more error handling to analyze-migration.py Fabiano Rosas
2025-01-10 12:14 ` [PULL 17/25] migration: Remove unused argument in vmsd_desc_field_end Fabiano Rosas
2025-01-10 12:14 ` [PULL 18/25] migration: Fix parsing of s390 stream Fabiano Rosas
2025-01-10 12:14 ` [PULL 19/25] migration: Rename vmstate_info_nullptr Fabiano Rosas
2025-01-10 12:14 ` [PULL 20/25] migration: Dump correct JSON format for nullptr replacement Fabiano Rosas
2025-01-10 12:14 ` [PULL 21/25] migration: Fix arrays of pointers in JSON writer Fabiano Rosas
2025-01-10 12:14 ` [PULL 22/25] s390x: Fix CSS migration Fabiano Rosas
2025-01-10 12:14 ` [PULL 23/25] multifd: bugfix for migration using compression methods Fabiano Rosas
2025-01-10 12:14 ` [PULL 24/25] multifd: bugfix for incorrect migration data with QPL compression Fabiano Rosas
2025-01-10 12:14 ` [PULL 25/25] multifd: bugfix for incorrect migration data with qatzip compression Fabiano Rosas
2025-01-12 15:37 ` Stefan Hajnoczi [this message]
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=20250112153735.GA31245@fedora \
--to=stefanha@redhat.com \
--cc=farosas@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.