From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 1/2] KVM: Document KVM_SET_USER_MEMORY_REGION Date: Thu, 25 Mar 2010 13:58:40 +0200 Message-ID: <4BAB4FF0.5060106@redhat.com> References: <1269513099-21060-1-git-send-email-avi@redhat.com> <1269513099-21060-2-git-send-email-avi@redhat.com> <794E62B0-9DD5-473A-BA3C-E6971E35D04D@suse.de> <4BAB4DE7.7090205@redhat.com> <310EF8EB-9271-4375-BB51-9FDBFD2F6576@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "kvm@vger.kernel.org" , Pekka Enberg , Marcelo Tosatti To: Alexander Graf Return-path: Received: from mx1.redhat.com ([209.132.183.28]:18052 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750967Ab0CYL6q (ORCPT ); Thu, 25 Mar 2010 07:58:46 -0400 In-Reply-To: <310EF8EB-9271-4375-BB51-9FDBFD2F6576@suse.de> Sender: kvm-owner@vger.kernel.org List-ID: On 03/25/2010 01:54 PM, Alexander Graf wrote: > > Am 25.03.2010 um 12:49 schrieb Avi Kivity : > >> On 03/25/2010 01:10 PM, Alexander Graf wrote: >>> >>> Am 25.03.2010 um 11:31 schrieb Avi Kivity : >>> >>>> >>>> +It is recommended to use this API instead of the >>>> KVM_SET_MEMORY_REGION ioctl. >>> >>> Why? What's wrong with SET_MEM_REGION? >>> >> >> It doesn't allow any control over the memory. So it found its way >> into Documentation/feature-removal-schedule.txt. > > Definitely worth adding to the above phrase then. > Will do. -- error compiling committee.c: too many arguments to function