From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NTyoi-0002Pw-Bn for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:30:56 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NTyod-0002Nv-Ae for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:30:55 -0500 Received: from [199.232.76.173] (port=54442 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NTyoc-0002Nn-W9 for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:30:51 -0500 Received: from mx1.redhat.com ([209.132.183.28]:26524) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NTyob-0006qA-No for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:30:50 -0500 Message-ID: <4B49E494.3030400@redhat.com> Date: Sun, 10 Jan 2010 16:30:44 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4B49C1D3.1070308@redhat.com> <20100110142820.GN4905@redhat.com> In-Reply-To: <20100110142820.GN4905@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: New kvm-related qemu patch queue List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: qemu-devel , KVM list On 01/10/2010 04:28 PM, Gleb Natapov wrote: > On Sun, Jan 10, 2010 at 02:02:27PM +0200, Avi Kivity wrote: > >> In order to improve qemu.git kvm integration quality wrt >> performance, features, and reliability Marcelo and I will begin to >> maintain a patch queue based on qemu.git containing kvm-related >> patches. We will review and apply patches to this queue, test them >> using the same test suite that is used for qemu-kvm.git, and >> regularly submit them for inclusion in qemu.git, mimicking the >> relationship between kvm.git and Linus' linux-2.6.git. >> >> One of the problems of qemu.git kvm support is that it is a clean >> reimplementation, and thus some of the nuances that were carefully >> ironed out in qemu-kvm.git are lost. To that end, we would like to >> change the process of adding features as follows: >> >> - first, the feature in qemu-kvm.git master is morphed to a form >> suitable for merging into qemu.git >> - when that has been accomplished, the feature is broken into >> patches and merged into the patch queue >> >> > If there is the same feature in qemu-kvm.git and qemu.git whom is morphed to > whom and who is merged where? I am confused. We have much of duplicated > code between qemu-kvm.git and qemu.git it is often almost, but not exactly the > same. Is it really productive to set rules who should be morphed and how > at this point? > If the feature is already in both, then morph qemu-kvm.git into what is already in qemu.git. Hopefully anything missing in qemu.git will be discovered while making the changes. >> In order to get a kvm feature into qemu.git, please observe the >> following process: >> >> - post a patch series against qemu-kvm.git/master that implements >> the feature, or changes an existing feature to use qemu.git >> infrastructure >> > It was other way around till last week. Why change? > There were a lot of regressions. -- error compiling committee.c: too many arguments to function