From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NTzA0-0006e0-U6
	for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:52:56 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1NTz9w-0006cs-GC
	for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:52:56 -0500
Received: from [199.232.76.173] (port=38955 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NTz9w-0006cp-Ak
	for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:52:52 -0500
Received: from mx1.redhat.com ([209.132.183.28]:27506)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <avi@redhat.com>) id 1NTz9v-0001R9-Nf
	for qemu-devel@nongnu.org; Sun, 10 Jan 2010 09:52:52 -0500
Message-ID: <4B49E9C0.1020108@redhat.com>
Date: Sun, 10 Jan 2010 16:52:48 +0200
From: Avi Kivity <avi@redhat.com>
MIME-Version: 1.0
References: <4B49C1D3.1070308@redhat.com> <20100110142820.GN4905@redhat.com>
	<4B49E494.3030400@redhat.com> <20100110144904.GO4905@redhat.com>
In-Reply-To: <20100110144904.GO4905@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: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gleb Natapov <gleb@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, KVM list <kvm@vger.kernel.org>

On 01/10/2010 04:49 PM, Gleb Natapov wrote:
>
>> 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.
>>
>>      
> What about bugs that are present only in qemu.git? Like this:
> http://patchwork.ozlabs.org/patch/42298/. Should it go through
> qemu-kvm.git/uq/master?
>    

Yes.  So there is a central place for kvm patches, and so they see autotest.


> What about this one: http://patchwork.ozlabs.org/patch/42447/ should it
> be postponed untill qemu.git and qemu-kvm.git converge on using the same
> cpuid infrastructure, or add similar functionality to qemu-kvm to,
> or add new cpu flags to qemu-kvm only and when cpuid code converge
> qemu.git will have it too?
>    

Best to make qemu-kvm.git and qemu.git converge first.  Duplicating the 
patch extends the problem.  Of course if something is urgent we can 
bypass the process.

-- 
error compiling committee.c: too many arguments to function