From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Juan Quintela <quintela@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com,
Leonardo Bras Soares Passos <lsoaresp@redhat.com>
Subject: [PATCH 0/7] migration: Postcopy cleanup on ram disgard
Date: Tue, 7 Dec 2021 19:50:09 +0800 [thread overview]
Message-ID: <20211207115016.73195-1-peterx@redhat.com> (raw)
Some queued patches for ram disgard cleanup, and some debug probes.
QEMU's ram disgard logic is probably a bit hard to predict because we send a
bunch of packets to notify the disgarded ranges rather than sending the bitmap.
The packets to send depending on the bitmap layout.
Initially I thought it could be a problem but in reality it's fine so far per
my initial measurement. So I'm flushing the cleanup/trace patches out because
I think they're still helpful.
Please have a look, thanks.
Peter Xu (7):
migration: Drop dead code of ram_debug_dump_bitmap()
migration: Don't return for postcopy_chunk_hostpages()
migration: Drop postcopy_chunk_hostpages()
migration: Do chunk page in postcopy_each_ram_send_discard()
migration: Drop return code for disgard ram process
migration: Dump sub-cmd name in loadvm_process_command tp
migration: Finer grained tracepoints for POSTCOPY_LISTEN
migration/migration.c | 5 +-
migration/ram.c | 103 ++++++-----------------------------------
migration/ram.h | 4 +-
migration/savevm.c | 7 ++-
migration/trace-events | 4 +-
5 files changed, 23 insertions(+), 100 deletions(-)
--
2.32.0
next reply other threads:[~2021-12-07 11:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 11:50 Peter Xu [this message]
2021-12-07 11:50 ` [PATCH 1/7] migration: Drop dead code of ram_debug_dump_bitmap() Peter Xu
2021-12-08 16:05 ` Dr. David Alan Gilbert
2022-01-26 21:02 ` Juan Quintela
2021-12-07 11:50 ` [PATCH 2/7] migration: Don't return for postcopy_chunk_hostpages() Peter Xu
2021-12-08 16:28 ` Dr. David Alan Gilbert
2022-01-26 21:03 ` Juan Quintela
2021-12-07 11:50 ` [PATCH 3/7] migration: Drop postcopy_chunk_hostpages() Peter Xu
2021-12-08 16:55 ` Dr. David Alan Gilbert
2022-01-26 21:14 ` Juan Quintela
2021-12-07 11:50 ` [PATCH 4/7] migration: Do chunk page in postcopy_each_ram_send_discard() Peter Xu
2021-12-08 17:39 ` Dr. David Alan Gilbert
2022-01-26 21:15 ` Juan Quintela
2021-12-07 11:50 ` [PATCH 5/7] migration: Drop return code for disgard ram process Peter Xu
2021-12-08 18:12 ` Dr. David Alan Gilbert
2022-01-26 21:17 ` Juan Quintela
2021-12-07 11:50 ` [PATCH 6/7] migration: Dump sub-cmd name in loadvm_process_command tp Peter Xu
2021-12-08 18:41 ` Dr. David Alan Gilbert
2021-12-09 1:44 ` Peter Xu
2021-12-07 11:50 ` [PATCH 7/7] migration: Finer grained tracepoints for POSTCOPY_LISTEN Peter Xu
2021-12-08 19:46 ` Dr. David Alan Gilbert
2021-12-09 1:54 ` Peter Xu
2021-12-09 9:04 ` Dr. David Alan Gilbert
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=20211207115016.73195-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lsoaresp@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).