From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pekka Enberg Subject: Re: [PATCH V2 04/23] kvm tools: Get correct 64-bit types on PPC64 and link appropriately Date: Mon, 12 Dec 2011 07:57:05 +0200 Message-ID: <1323669425.1428.292.camel@jaguar> References: <4EE1B07E.6070003@ozlabs.org> <1323419056.32487.17.camel@lappy> <4EE552FF.5070007@ozlabs.org> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 7bit Cc: Sasha Levin , kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, asias.hejun@gmail.com, gorcunov@gmail.com To: Matt Evans Return-path: In-Reply-To: <4EE552FF.5070007@ozlabs.org> Sender: kvm-ppc-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Mon, 2011-12-12 at 12:03 +1100, Matt Evans wrote: > On 09/12/11 19:29, Pekka Enberg wrote: > > On Fri, Dec 9, 2011 at 10:24 AM, Sasha Levin wrote: > >> If you also got kernel patches that add __SANE_USERSPACE_TYPES__ to the > >> headers, and KVM_CAP_NR_VCPUS to KVM PPC, we can carry them in the KVM > >> tools tree as well. > > > > Yup, all we need is ACKs from PPC maintainers. > > Cool, I've pinged them re. __SANE_USERSPACE_TYPES__, and that would be useful to > carry in your tree. But, IMHO, the patch I sent to Alex ("[PATCH] KVM: PPC: Add > KVM_CAP_NR_VCPUS and KVM_CAP_MAX_VCPUS") should go in via his tree. The > KVM/PPC-HV kernel folk will get it quicker in their trees (pulled from Alex) and > it's not a build problem, "only" a limit of SMP CPU numbers. That is, if you're > building a kernel for PPC KVM today you'll probably use something more similar > to Alex's tree than mainline/kvm tools tree. Definitely. The __SANE_USERSPACE_TYPES__ patch should probably go to powerpc git tree in addition to our tree. Pekka