From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Mackerras Subject: Re: [PATCH 0/13] Hypervisor-mode KVM on POWER7 Date: Thu, 19 May 2011 15:22:46 +1000 Message-ID: <20110519052246.GA8165@drongo> References: <20110511103443.GA2837@brick.ozlabs.ibm.com> <764651B6-6DDA-49DC-AA95-52CD86FF82D9@suse.de> <20110517111536.GC7924@brick.ozlabs.ibm.com> <14CFAA70-1747-4902-8CC1-4BE924CAD031@suse.de> <4DD25F10.4030707@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Alexander Graf , "linuxppc-dev@ozlabs.org" , "kvm@vger.kernel.org" To: Avi Kivity Return-path: Received: from ozlabs.org ([203.10.76.45]:43311 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752442Ab1ESFWx (ORCPT ); Thu, 19 May 2011 01:22:53 -0400 Content-Disposition: inline In-Reply-To: <4DD25F10.4030707@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, May 17, 2011 at 02:42:08PM +0300, Avi Kivity wrote: > On 05/17/2011 02:38 PM, Alexander Graf wrote: > >> > >> What would be the path for these patches to get upstream? Would this > >> stuff normally go through Avi's tree? There is a bit of a > >> complication in that they are based on Ben's next branch. Would Avi > >> pull Ben's next branch, or would they go in via Ben's tree? > > > >Usually the ppc tree gets merged into Avi's tree and goes on from > >there. When we have interdependencies, we can certainly do it > >differently though. We can also shove them through Ben's tree this > >time around, as there are more dependencies on ppc code than KVM > >code. > > > > Yes, both options are fine. If it goes through kvm.git I can merge > Ben's tree (provided it is append-only) and apply the kvm-ppc > patches on top. OK, the easiest thing is for them to go via Ben's tree, I think, since they depend so much on other stuff in Ben's tree. Alex, could you give Ben an acked-by for patches 1-8 of the series? There haven't been any changes requested for them. Thanks, Paul.