public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: David Hildenbrand <david@redhat.com>, qemu-devel@nongnu.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>, kvm@vger.kernel.org
Subject: Re: [PATCH v1 0/6] QEMU: kvm: cleanup kvm_slot handling
Date: Tue, 12 Sep 2017 09:39:50 +0200	[thread overview]
Message-ID: <55ff3bc7-6e83-5347-4a7d-e77058e84abc@redhat.com> (raw)
In-Reply-To: <20170911174933.20789-1-david@redhat.com>

On 11/09/2017 19:49, David Hildenbrand wrote:
> 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).
> 
> 
> RFC -> v1:
> - minor changes to avoid changing indentation, therefore making it easier
>   to review

Queued, thanks!

Paolo

> 
> 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 | 235 +++++++++++++++-------------------------------------
>  1 file changed, 68 insertions(+), 167 deletions(-)
> 

      parent reply	other threads:[~2017-09-12  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-11 17:49 [PATCH v1 0/6] QEMU: kvm: cleanup kvm_slot handling David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 1/6] kvm: require JOIN_MEMORY_REGIONS_WORKS David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 2/6] kvm: factor out alignment of memory section David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 3/6] kvm: use start + size for memory ranges David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 4/6] kvm: we never have overlapping slots in kvm_set_phys_mem() David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 5/6] kvm: kvm_log_start/stop are only called with known sections David Hildenbrand
2017-10-10  9:06   ` [Qemu-devel] " Thomas Huth
2017-10-10 13:29     ` Paolo Bonzini
2017-10-16  7:16       ` David Hildenbrand
2017-10-16  8:52         ` Thomas Huth
2017-10-16  9:19           ` David Hildenbrand
2017-09-11 17:49 ` [PATCH v1 6/6] kvm: kvm_log_sync() is only called with known memory sections David Hildenbrand
2017-09-12  7:39 ` Paolo Bonzini [this message]

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=55ff3bc7-6e83-5347-4a7d-e77058e84abc@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rkrcmar@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