From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH] KVM: Remove user_alloc from struct kvm_memory_slot Date: Fri, 8 Feb 2013 21:32:43 -0200 Message-ID: <20130208233243.GA29339@amt.cnet> References: <20130207185557.b32ba396.yoshikawa_takuya_b1@lab.ntt.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: gleb@redhat.com, kvm@vger.kernel.org To: Takuya Yoshikawa Return-path: Received: from mx1.redhat.com ([209.132.183.28]:31165 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1947302Ab3BHXcz (ORCPT ); Fri, 8 Feb 2013 18:32:55 -0500 Content-Disposition: inline In-Reply-To: <20130207185557.b32ba396.yoshikawa_takuya_b1@lab.ntt.co.jp> Sender: kvm-owner@vger.kernel.org List-ID: On Thu, Feb 07, 2013 at 06:55:57PM +0900, Takuya Yoshikawa wrote: > This field was needed to differentiate memory slots created by the new > API, KVM_SET_USER_MEMORY_REGION, from those by the old equivalent, > KVM_SET_MEMORY_REGION, whose support was dropped long before: > > commit b74a07beed0e64bfba413dcb70dd6749c57f43dc > KVM: Remove kernel-allocated memory regions > > Although we also have private memory slots to which KVM allocates > memory with vm_mmap(), !user_alloc slots in other words, the slot id > should be enough for differentiating them. > > Note: corresponding function parameters will be removed later. > > Signed-off-by: Takuya Yoshikawa Reviewed-by: Marcelo Tosatti