From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Dr . David Alan Gilbert" <dgilbert@redhat.com>,
peterx@redhat.com, "David Hildenbrand" <david@redhat.com>
Subject: [PATCH RESEND 0/2] memory: Add tracepoints for log_sync
Date: Mon, 16 Aug 2021 21:35:51 -0400 [thread overview]
Message-ID: <20210817013553.30584-1-peterx@redhat.com> (raw)
[this is a resend to hopefully drop '\r' in cover letter caused by git-publish
that I should have just fixed; nothing changed inside]
It can help to identify which step is slow for migration dirty sync process.
We have migration_bitmap_sync_* trace events but it's still a bit coarse.
This should help us to cut migration_bitmap_sync() into finer grained small
steps when measurement is needed.
Please review, thanks.
Peter Xu (2):
memory: Name all the memory listeners
memory: Add tracepoint for dirty sync
accel/hvf/hvf-accel-ops.c | 1 +
accel/kvm/kvm-all.c | 7 +++++--
hw/i386/xen/xen-hvm.c | 2 ++
hw/intc/openpic_kvm.c | 1 +
hw/remote/proxy-memory-listener.c | 1 +
hw/vfio/common.c | 1 +
hw/vfio/spapr.c | 1 +
hw/virtio/vhost-vdpa.c | 1 +
hw/virtio/vhost.c | 2 ++
hw/virtio/virtio.c | 1 +
hw/xen/xen_pt.c | 2 ++
include/exec/memory.h | 8 ++++++++
include/sysemu/kvm_int.h | 2 +-
softmmu/memory.c | 2 ++
softmmu/physmem.c | 1 +
softmmu/trace-events | 1 +
target/arm/kvm.c | 1 +
target/i386/hax/hax-mem.c | 1 +
target/i386/kvm/kvm.c | 2 +-
target/i386/nvmm/nvmm-all.c | 1 +
target/i386/whpx/whpx-all.c | 1 +
21 files changed, 36 insertions(+), 4 deletions(-)
--
2.31.1
next reply other threads:[~2021-08-17 1:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-17 1:35 Peter Xu [this message]
2021-08-17 1:35 ` [PATCH RESEND 1/2] memory: Name all the memory listeners Peter Xu
2021-08-17 7:24 ` David Hildenbrand
2021-08-17 1:37 ` [PATCH RESEND 2/2] memory: Add tracepoint for dirty sync Peter Xu
2021-08-17 7:25 ` David Hildenbrand
2021-08-17 16:05 ` Peter Xu
2021-08-17 16:07 ` David Hildenbrand
2021-09-20 13:01 ` Paolo Bonzini
2021-09-20 12:59 ` Paolo Bonzini
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=20210817013553.30584-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@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).