From: Juan Quintela <quintela@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Juan Quintela <quintela@redhat.com>
Subject: [PULL 0/7] Migration.next patches
Date: Tue, 19 Oct 2021 11:29:00 +0200 [thread overview]
Message-ID: <20211019092907.5255-1-quintela@redhat.com> (raw)
The following changes since commit 362534a643b4a34bcb223996538ce9de5cdab946:
Merge remote-tracking branch 'remotes/bsdimp/tags/pull-bsd-user-20211018-pull-request' into staging (2021-10-18 12:17:24 -0700)
are available in the Git repository at:
https://github.com/juanquintela/qemu.git tags/migration.next-pull-request
for you to fetch changes up to 911965ace9386e35ca022a65bb45a32fd421af3e:
migration/rdma: advise prefetch write for ODP region (2021-10-19 08:39:04 +0200)
----------------------------------------------------------------
Migration Pull request (3rd try)
Hi
This should fix all the freebsd problems.
Please apply,
----------------------------------------------------------------
David Hildenbrand (1):
migration/ram: Don't passs RAMState to
migration_clear_memory_region_dirty_bitmap_*()
Li Zhijian (4):
migration: allow multifd for socket protocol only
migration: allow enabling mutilfd for specific protocol only
migration/rdma: Try to register On-Demand Paging memory region
migration/rdma: advise prefetch write for ODP region
Lukas Straub (2):
multifd: Implement yank for multifd send side
multifd: Unconditionally unregister yank function
meson.build | 6 +++
migration/multifd.h | 4 ++
migration/migration.c | 12 +++++
migration/multifd.c | 35 ++++++++++---
migration/ram.c | 13 ++---
migration/rdma.c | 113 ++++++++++++++++++++++++++++++++++-------
migration/trace-events | 2 +
7 files changed, 151 insertions(+), 34 deletions(-)
--
2.31.1
next reply other threads:[~2021-10-19 9:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 9:29 Juan Quintela [this message]
2021-10-19 9:29 ` [PULL 1/7] multifd: Implement yank for multifd send side Juan Quintela
2021-10-19 9:29 ` [PULL 2/7] multifd: Unconditionally unregister yank function Juan Quintela
2021-10-19 9:29 ` [PULL 3/7] migration/ram: Don't passs RAMState to migration_clear_memory_region_dirty_bitmap_*() Juan Quintela
2021-10-19 9:29 ` [PULL 4/7] migration: allow multifd for socket protocol only Juan Quintela
2021-10-19 9:29 ` [PULL 5/7] migration: allow enabling mutilfd for specific " Juan Quintela
2021-10-19 9:29 ` [PULL 6/7] migration/rdma: Try to register On-Demand Paging memory region Juan Quintela
2021-10-19 9:29 ` [PULL 7/7] migration/rdma: advise prefetch write for ODP region Juan Quintela
2021-10-19 16:55 ` [PULL 0/7] Migration.next patches Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2021-09-09 10:33 Juan Quintela
2021-09-09 13:42 ` Peter Maydell
2021-09-09 14:48 ` Li, Zhijian
2021-09-09 14:59 ` Peter Maydell
2021-09-09 15:23 ` Juan Quintela
2021-09-09 15:36 ` Peter Maydell
2021-09-09 16:10 ` Juan Quintela
2021-09-10 5:20 ` lizhijian
2021-09-10 5:27 ` lizhijian
2021-09-10 7:00 ` Juan Quintela
2021-09-10 8:52 ` lizhijian
2021-09-10 12:55 ` Philippe Mathieu-Daudé
2021-09-10 13:10 ` Li, Zhijian
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=20211019092907.5255-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).