From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([140.186.70.92]:58067)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1Rl4Qd-00050v-GE
	for qemu-devel@nongnu.org; Wed, 11 Jan 2012 15:05:48 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1Rl4Qc-0002O8-Cv
	for qemu-devel@nongnu.org; Wed, 11 Jan 2012 15:05:47 -0500
Received: from cantor2.suse.de ([195.135.220.15]:52282 helo=mx2.suse.de)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <agraf@suse.de>) id 1Rl4Qc-0002O1-3s
	for qemu-devel@nongnu.org; Wed, 11 Jan 2012 15:05:46 -0500
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=us-ascii
From: Alexander Graf <agraf@suse.de>
In-Reply-To: <4F0DEA28.9010700@codemonkey.ws>
Date: Wed, 11 Jan 2012 21:05:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <AD835CAF-820F-41EA-978D-1C7AED1B0BE3@suse.de>
References: <4F0DE028.4050707@siemens.com>	<A89B3EE9-1CCD-4DBD-9459-6104F82B4A13@suse.de>	<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>
Subject: Re: [Qemu-devel] State of KVM bits in linux-headers
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, Marcelo Tosatti <mtosatti@redhat.com>, qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>, Avi Kivity <avi@redhat.com>


On 11.01.2012, at 20:59, Anthony Liguori wrote:

> On 01/11/2012 01:53 PM, Alexander Graf wrote:
>>=20
>> On 11.01.2012, at 20:52, Anthony Liguori wrote:
>>=20
>>>> IIRC, we never had this problem with qemu-kvm - as the merges were
>>>> coordinated with the kernel (subsystem) tree.
>>>=20
>>> Are you suggesting that kvm header updates go through uq/master?  =
That seems reasonable to me and is certainly the least amount of change.
>>=20
>> So how about code that actually leverages the new headers?
>=20
> Shared KVM infrastructure should go through uq/master.  So changes to =
kvm-all.c, linux-headers/* should go through uq/master.
>=20
> Target specific kvm changes should go through the appropriate =
submaintainers tree.

So then if I add some target specific stuff to KVM, I have to

  * send pullreq to KVM
  * wait for that to be applied
  * post a patch to uq/master to update headers
  * wait for that to merge back to qemu.git
  * send a pull request to qemu.git

right? And then after about 3 months we'll have the feature available =
;).


Alex