From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, david@redhat.com
Subject: [PATCH RFC 0/6] QEMU: kvm: cleanup kvm_slot handling
Date: Wed, 9 Aug 2017 15:33:40 +0200 [thread overview]
Message-ID: <20170809133346.30271-1-david@redhat.com> (raw)
If I am not missing something important here, we can heavily simplify
the kvm_slot code. Flatview will make sure that we don't have to deal
with overlapping slots. E.g. when a memory section is resized, we are
first notified about the removal and then about the new memory section.
So basically, we can directly always map one memory section to one
kvm slot (if the fixed up size is > 0).
Only very briefly tested. Will do some more testing if we agree that this
is the right thing to do.
David Hildenbrand (6):
kvm: require JOIN_MEMORY_REGIONS_WORKS
kvm: factor out alignment of memory section
kvm: use start + size for memory ranges
kvm: we never have overlapping slots in kvm_set_phys_mem()
kvm: kvm_log_start/stop are only called with known sections
kvm: kvm_log_sync() is only called with known memory sections
accel/kvm/kvm-all.c | 276 +++++++++++++++++-----------------------------------
1 file changed, 89 insertions(+), 187 deletions(-)
--
2.9.4
next reply other threads:[~2017-08-09 13:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 13:33 David Hildenbrand [this message]
2017-08-09 13:33 ` [PATCH RFC 1/6] kvm: require JOIN_MEMORY_REGIONS_WORKS David Hildenbrand
2017-08-09 13:33 ` [PATCH RFC 2/6] kvm: factor out alignment of memory section David Hildenbrand
2017-08-09 13:33 ` [PATCH RFC 3/6] kvm: use start + size for memory ranges David Hildenbrand
2017-08-09 13:33 ` [PATCH RFC 4/6] kvm: we never have overlapping slots in kvm_set_phys_mem() David Hildenbrand
2017-08-09 13:33 ` [PATCH RFC 5/6] kvm: kvm_log_start/stop are only called with known sections David Hildenbrand
2017-08-09 13:33 ` [PATCH RFC 6/6] kvm: kvm_log_sync() is only called with known memory sections David Hildenbrand
2017-08-09 16:49 ` [PATCH RFC 0/6] QEMU: kvm: cleanup kvm_slot handling 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=20170809133346.30271-1-david@redhat.com \
--to=david@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@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