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 v2 0/8] migration: Postcopy cleanup on ram disgard
Date: Mon, 20 Dec 2021 16:53:47 +0800 [thread overview]
Message-ID: <20211220085355.2284-1-peterx@redhat.com> (raw)
v2:
- add r-bs for Dave
- move mig_cmd_args reference later than index bound check [Dave]
- use chars in tracepoints instead of number of steps [Dave]
- add one patch for postcopy-run tracing
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 (8):
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: Tracepoint change in postcopy-run bottom half
migration/migration.c | 5 +-
migration/ram.c | 103 ++++++-----------------------------------
migration/ram.h | 4 +-
migration/savevm.c | 24 ++++++++--
migration/trace-events | 7 ++-
5 files changed, 38 insertions(+), 105 deletions(-)
--
2.32.0
next reply other threads:[~2021-12-20 16:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-20 8:53 Peter Xu [this message]
2021-12-20 8:53 ` [PATCH v2 1/8] migration: Drop dead code of ram_debug_dump_bitmap() Peter Xu
2021-12-20 8:53 ` [PATCH v2 2/8] migration: Don't return for postcopy_chunk_hostpages() Peter Xu
2021-12-20 8:53 ` [PATCH v2 3/8] migration: Drop postcopy_chunk_hostpages() Peter Xu
2021-12-20 8:53 ` [PATCH v2 4/8] migration: Do chunk page in postcopy_each_ram_send_discard() Peter Xu
2021-12-20 8:53 ` [PATCH v2 5/8] migration: Drop return code for disgard ram process Peter Xu
2021-12-20 8:53 ` [PATCH v2 6/8] migration: Dump sub-cmd name in loadvm_process_command tp Peter Xu
2021-12-21 10:08 ` David Edmondson
2021-12-21 12:59 ` Peter Xu
2021-12-20 8:53 ` [PATCH v2 7/8] migration: Finer grained tracepoints for POSTCOPY_LISTEN Peter Xu
2021-12-21 10:12 ` David Edmondson
2021-12-21 13:08 ` Peter Xu
2021-12-20 8:53 ` [PATCH v2 8/8] migration: Tracepoint change in postcopy-run bottom half Peter Xu
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=20211220085355.2284-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).