From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v7 00/12] KVM/ARM Implementation Date: Mon, 12 Mar 2012 19:36:09 +0200 Message-ID: <4F5E3409.90408@redhat.com> References: <20120312065134.8074.36949.stgit@ubuntu> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: android-virt@lists.cs.columbia.edu, kvm@vger.kernel.org, tech@virtualopensystems.com To: Christoffer Dall Return-path: Received: from mx1.redhat.com ([209.132.183.28]:21008 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751582Ab2CLRgU (ORCPT ); Mon, 12 Mar 2012 13:36:20 -0400 In-Reply-To: <20120312065134.8074.36949.stgit@ubuntu> Sender: kvm-owner@vger.kernel.org List-ID: On 03/12/2012 08:51 AM, Christoffer Dall wrote: > The following series implements KVM support for ARM processors, > specifically on the Cortex A-15 platform. > > The patch series applies to a mashup of v3.3-rc6, the vexpress support, > and kvm-next. I apologize for this mess, but there's really no good way > around this, since we need vexpress support and we want to keep up with > kvm-next for QEMU support. That's not a mess, that's how distributed development works. Note you could base your patches on linux-next, if it includes vexpress support, since it already includes kvm.git next (with some lag). In any case basing patches on a merge of all required trees is fine. > Changes since v6: > - Support for MMU notifiers to not pin user pages in memory Nice! As I repeat at every possible opportunity, mmu notifiers are a big part of what makes kvm successful. -- error compiling committee.c: too many arguments to function