From: Peter Xu <peterx@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vitaly Kuznetsov <vkuznets@redhat.com>,
David Hildenbrand <david@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
peterx@redhat.com, Prasad Pandit <ppandit@redhat.com>,
Juraj Marcin <jmarcin@redhat.com>,
Julia Suvorova <jusual@redhat.com>,
Fabiano Rosas <farosas@suse.de>
Subject: [PATCH v3 0/4] KVM: Dynamic sized memslots array
Date: Mon, 9 Sep 2024 10:54:09 -0400 [thread overview]
Message-ID: <20240909145413.3748429-1-peterx@redhat.com> (raw)
v3:
- In kvm_get_free_slot(), avoid re-search when slots array grows [Juraj]
v1: https://lore.kernel.org/r/20240904191635.3045606-1-peterx@redhat.com
v2: https://lore.kernel.org/r/20240904223510.3519358-1-peterx@redhat.com
This series make KVM memslots to be allocated dynamically in QEMU. It
fixes a migration performance regression that I observed, reducing precopy
dirty sync process from ~86ms to ~3ms each time.
Patch 1 is the fix to the problem, while the rest three patches are
cleanups.
Thanks,
Peter Xu (4):
KVM: Dynamic sized kvm memslots array
KVM: Define KVM_MEMSLOTS_NUM_MAX_DEFAULT
KVM: Rename KVMMemoryListener.nr_used_slots to nr_slots_used
KVM: Rename KVMState->nr_slots to nr_slots_max
include/sysemu/kvm_int.h | 7 ++-
accel/kvm/kvm-all.c | 117 +++++++++++++++++++++++++++++++--------
accel/kvm/trace-events | 1 +
3 files changed, 99 insertions(+), 26 deletions(-)
--
2.45.0
next reply other threads:[~2024-09-09 14:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 14:54 Peter Xu [this message]
2024-09-09 14:54 ` [PATCH v3 1/4] KVM: Dynamic sized kvm memslots array Peter Xu
2024-09-16 17:47 ` Fabiano Rosas
2024-09-16 17:52 ` Fabiano Rosas
2024-09-17 15:52 ` Peter Xu
2024-09-09 14:54 ` [PATCH v3 2/4] KVM: Define KVM_MEMSLOTS_NUM_MAX_DEFAULT Peter Xu
2024-09-09 14:54 ` [PATCH v3 3/4] KVM: Rename KVMMemoryListener.nr_used_slots to nr_slots_used Peter Xu
2024-09-09 14:54 ` [PATCH v3 4/4] KVM: Rename KVMState->nr_slots to nr_slots_max 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=20240909145413.3748429-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=david@redhat.com \
--cc=farosas@suse.de \
--cc=jmarcin@redhat.com \
--cc=jusual@redhat.com \
--cc=pbonzini@redhat.com \
--cc=ppandit@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vkuznets@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).