From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 10/14] KVM: PPC: Enable the PAPR CAP for Book3S Date: Wed, 31 Aug 2011 11:39:31 +0300 Message-ID: <4E5DF343.2050506@redhat.com> References: <1314283193-10323-1-git-send-email-agraf@suse.de> <1314283193-10323-11-git-send-email-agraf@suse.de> <4E5DF172.9070207@redhat.com> <0A9D1F7F-7516-4186-98F0-7CB70FA35BDA@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, kvm-ppc@vger.kernel.org To: Alexander Graf Return-path: In-Reply-To: <0A9D1F7F-7516-4186-98F0-7CB70FA35BDA@suse.de> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/31/2011 11:37 AM, Alexander Graf wrote: > On 31.08.2011, at 10:31, Avi Kivity wrote: > > > On 08/25/2011 05:39 PM, Alexander Graf wrote: > >> Now that Book3S PV mode can also run PAPR guests, we can add a PAPR cap and > >> enable it for all Book3S targets. Enabling that CAP switches KVM into PAPR > >> mode. > >> > >> #define KVM_CAP_PPC_RMA 65 > >> #define KVM_CAP_MAX_VCPUS 66 /* returns max vcpus per vm */ > >> #define KVM_CAP_PPC_HIOR 67 > >> +#define KVM_CAP_PPC_PAPR 68 > >> > >> #ifdef KVM_CAP_IRQ_ROUTING > >> > > > > Documentation/virtual/kvm/api.txt > > Yeah, we don't have a section for capabilities that don't have their own ioctls yet, so I didn't add it. I can create one if you like. > Please do. -- error compiling committee.c: too many arguments to function