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 <yoshikawa_takuya_b1@xxxxxxxxxxxxx> Reviewed-by: Marcelo Tosatti <mtosatti@xxxxxxxxxx> -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
