From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [Qemu-devel] State of KVM bits in linux-headers Date: Wed, 11 Jan 2012 14:16:56 -0600 Message-ID: <4F0DEE38.6060100@codemonkey.ws> References: <4F0DE028.4050707@siemens.com> <4F0DE54F.1050700@siemens.com> <4F0DE5F2.7090001@codemonkey.ws> <7780A9ED-CF05-41D8-8521-FDAEAC984EB7@suse.de> <4F0DE7A4.5050000@siemens.com> <4F0DE867.6030303@codemonkey.ws> <59344EBA-23C4-4D25-9802-C627AAB8FFFA@suse.de> <4F0DEA28.9010700@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Jan Kiszka , Marcelo Tosatti , qemu-devel , kvm , Avi Kivity To: Alexander Graf Return-path: Received: from mail-gx0-f174.google.com ([209.85.161.174]:38112 "EHLO mail-gx0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757871Ab2AKURC (ORCPT ); Wed, 11 Jan 2012 15:17:02 -0500 Received: by ggdk6 with SMTP id k6so582361ggd.19 for ; Wed, 11 Jan 2012 12:17:01 -0800 (PST) In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 01/11/2012 02:05 PM, Alexander Graf wrote: > > On 11.01.2012, at 20:59, Anthony Liguori wrote: > >> On 01/11/2012 01:53 PM, Alexander Graf wrote: >>> >>> On 11.01.2012, at 20:52, Anthony Liguori wrote: >>> >>>>> IIRC, we never had this problem with qemu-kvm - as the merges were >>>>> coordinated with the kernel (subsystem) tree. >>>> >>>> Are you suggesting that kvm header updates go through uq/master? That seems reasonable to me and is certainly the least amount of change. >>> >>> So how about code that actually leverages the new headers? >> >> Shared KVM infrastructure should go through uq/master. So changes to kvm-all.c, linux-headers/* should go through uq/master. >> >> Target specific kvm changes should go through the appropriate submaintainers tree. > > So then if I add some target specific stuff to KVM, That requires a header update? > I have to > > * send pullreq to KVM > * wait for that to be applied > * post a patch to uq/master to update headers Strictly from a QEMU perspective, we can't depend on APIs that aren't committed upstream yet. > * wait for that to merge back to qemu.git > * send a pull request to qemu.git Maybe we need to bring a stripped down version of Linux into qemu.git to make it easier to simultaneously update both trees... ;-) > > right? And then after about 3 months we'll have the feature available ;). You can always just get Acked-by's from the appropriate maintainers. That's just as good as going through the tree. Regards, Anthony Liguori > > Alex > >