From: Paolo Bonzini Subject: Re: [PATCH v1 0/6] QEMU: kvm: cleanup kvm_slot handling Date: Tue, 12 Sep 2017 09:39:50 +0200 Message-ID: <55ff3bc7-6e83-5347-4a7d-e77058e84abc@redhat.com> References: <20170911174933.20789-1-david@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: =?UTF-8?B?UmFkaW0gS3LEjW3DocWZ?= , kvm@vger.kernel.org To: David Hildenbrand , qemu-devel@nongnu.org Return-path: Received: from mx1.redhat.com ([209.132.183.28]:33850 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751141AbdILHkD (ORCPT ); Tue, 12 Sep 2017 03:40:03 -0400 In-Reply-To: <20170911174933.20789-1-david@redhat.com> Content-Language: en-US Sender: kvm-owner@vger.kernel.org List-ID: 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(-) >