From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: [PULL 0/7] Migration 20230316 patches
Date: Thu, 16 Mar 2023 16:12:18 +0100 [thread overview]
Message-ID: <20230316151225.11362-1-quintela@redhat.com> (raw)
The following changes since commit 9636e513255362c4a329e3e5fb2c97dab3c5ce47:
Merge tag 'misc-next-pull-request' of https://gitlab.com/berrange/qemu into staging (2023-03-15 17:20:04 +0000)
are available in the Git repository at:
https://gitlab.com/juan.quintela/qemu.git tags/migration-20230316-pull-request
for you to fetch changes up to fa76c854ae837328187bef41d80af5d1ad36681f:
migration: fix populate_vfio_info (2023-03-16 16:07:07 +0100)
----------------------------------------------------------------
Migration Pull request
Hi
This is just fixes for migration.
- Fix rdma (dave)
- Remove unused variable (Zhijian)
- Fix AVX512 and XBZRLE (Matheus)
- Fix migration preempt (Peter)
- Fix populate_vfio_info (Steve)
- Fix multifd send trace (Wei)
Please apply.
Later, Juan.
----------------------------------------------------------------
Dr. David Alan Gilbert (1):
migration/rdma: Fix return-path case
Li Zhijian (1):
migration/rdma: Remove deprecated variable rdma_return_path
Matheus Tavares Bernardino (2):
migration/xbzrle: use ctz64 to avoid undefined result
migration/xbzrle: fix out-of-bounds write with axv512
Peter Xu (1):
migration: Wait on preempt channel in preempt thread
Steve Sistare (1):
migration: fix populate_vfio_info
Wei Wang (1):
migration/multifd: correct multifd_send_thread to trace the flags
migration/multifd.c | 3 ++-
migration/postcopy-ram.c | 11 ++++++-----
migration/rdma.c | 11 ++++++-----
migration/target.c | 2 +-
migration/xbzrle.c | 12 ++++++------
5 files changed, 21 insertions(+), 18 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-16 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 15:12 Juan Quintela [this message]
2023-03-16 15:12 ` [PULL 1/7] migration: Wait on preempt channel in preempt thread Juan Quintela
2023-03-16 15:12 ` [PULL 2/7] migration/rdma: Fix return-path case Juan Quintela
2023-03-16 15:12 ` [PULL 3/7] migration/xbzrle: use ctz64 to avoid undefined result Juan Quintela
2023-03-16 15:12 ` [PULL 4/7] migration/xbzrle: fix out-of-bounds write with axv512 Juan Quintela
2023-03-16 15:12 ` [PULL 5/7] migration/rdma: Remove deprecated variable rdma_return_path Juan Quintela
2023-03-16 15:12 ` [PULL 6/7] migration/multifd: correct multifd_send_thread to trace the flags Juan Quintela
2023-03-16 15:12 ` [PULL 7/7] migration: fix populate_vfio_info Juan Quintela
2023-03-17 13:11 ` [PULL 0/7] Migration 20230316 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=20230316151225.11362-1-quintela@redhat.com \
--to=quintela@redhat.com \
--cc=dgilbert@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).