From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Xu Date: Tue, 17 Dec 2019 22:07:18 +0000 Subject: Re: [PATCH v4 05/19] KVM: x86: Allocate memslot resources during prepare_memory_region() Message-Id: <20191217220718.GJ7258@xz-x1> List-Id: References: <20191217204041.10815-1-sean.j.christopherson@intel.com> <20191217204041.10815-6-sean.j.christopherson@intel.com> In-Reply-To: <20191217204041.10815-6-sean.j.christopherson@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Sean Christopherson Cc: James Hogan , Paul Mackerras , Christian Borntraeger , Janosch Frank , Paolo Bonzini , Marc Zyngier , linux-arm-kernel@lists.infradead.org, Wanpeng Li , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= , kvm@vger.kernel.org, David Hildenbrand , Joerg Roedel , Cornelia Huck , linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org, kvm-ppc@vger.kernel.org, Vitaly Kuznetsov , kvmarm@lists.cs.columbia.edu, Jim Mattson On Tue, Dec 17, 2019 at 12:40:27PM -0800, Sean Christopherson wrote: > Allocate the various metadata structures associated with a new memslot > during kvm_arch_prepare_memory_region(), which paves the way for > removing kvm_arch_create_memslot() altogether. Moving x86's memory > allocation only changes the order of kernel memory allocations between > x86 and common KVM code. > > No functional change intended. (I still think it's a functional change, though...) > > Signed-off-by: Sean Christopherson Reviewed-by: Peter Xu -- Peter Xu