From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ingo Molnar Subject: Re: [PATCH RFC V11 15/18] kvm : Paravirtual ticketlocks support for linux guests running on KVM hypervisor Date: Mon, 5 Aug 2013 15:52:22 +0200 Message-ID: <20130805135222.GA32429@gmail.com> References: <51F0ED31.3040200@linux.vnet.ibm.com> <20130725091509.GA22735@redhat.com> <51F0F202.5090001@linux.vnet.ibm.com> <51F7ED20.80202@linux.vnet.ibm.com> <20130731062440.GK28372@redhat.com> <51FA1087.9080908@linux.vnet.ibm.com> <20130802092539.GB28327@gmail.com> <20130802095406.GB30072@redhat.com> <20130805094603.GA29303@gmail.com> <20130805095901.GL2258@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20130805095901.GL2258@redhat.com> Sender: kvm-owner@vger.kernel.org To: Gleb Natapov Cc: Raghavendra K T , mingo@redhat.com, x86@kernel.org, tglx@linutronix.de, jeremy@goop.org, konrad.wilk@oracle.com, hpa@zytor.com, pbonzini@redhat.com, linux-doc@vger.kernel.org, habanero@linux.vnet.ibm.com, xen-devel@lists.xensource.com, peterz@infradead.org, mtosatti@redhat.com, stefano.stabellini@eu.citrix.com, andi@firstfloor.org, attilio.rao@citrix.com, ouyang@cs.pitt.edu, gregkh@suse.de, agraf@suse.de, chegu_vinod@hp.com, torvalds@linux-foundation.org, avi.kivity@gmail.com, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, riel@redhat.com, drjones@redhat.com, virtualization@lists.linux-foundation.org, srivatsa.vaddagiri@gmail.com List-Id: xen-devel@lists.xenproject.org * Gleb Natapov wrote: > On Mon, Aug 05, 2013 at 11:46:03AM +0200, Ingo Molnar wrote: > > Acked-by: Ingo Molnar > > > > I guess you'd want to carry this in the KVM tree or so - maybe in a > > separate branch because it changes Xen as well? > > It changes KVM host and guest side, XEN and common x86 spinlock code. I > think it would be best to merge common x86 spinlock bits and guest side > KVM/XEN bits through tip tree and host KVM part will go through KVM > tree. If this is OK with you, Ingo, and XEN folks Raghavendra can send > two separate patch series one for the tip and one for KVM host side. Sure, that's fine - if the initial series works fine in isolation as well (i.e. won't break anything). Thanks, Ingo