From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1MTgee-0001fl-22
	for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:35:04 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1MTgeZ-0001bH-Co
	for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:35:03 -0400
Received: from [199.232.76.173] (port=49946 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1MTgeZ-0001b6-6S
	for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:34:59 -0400
Received: from e34.co.us.ibm.com ([32.97.110.152]:44113)
	by monty-python.gnu.org with esmtps
	(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60)
	(envelope-from <aliguori@us.ibm.com>) id 1MTgeY-0008Sf-S0
	for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:34:59 -0400
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com
	[9.17.195.107])
	by e34.co.us.ibm.com (8.14.3/8.13.1) with ESMTP id n6MIRGKf011130
	for <qemu-devel@nongnu.org>; Wed, 22 Jul 2009 12:27:16 -0600
Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168])
	by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id
	n6MIUVMv115730
	for <qemu-devel@nongnu.org>; Wed, 22 Jul 2009 12:30:31 -0600
Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1])
	by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id
	n6MIUUkL006262
	for <qemu-devel@nongnu.org>; Wed, 22 Jul 2009 12:30:30 -0600
Message-ID: <4A675AC4.1000701@us.ibm.com>
Date: Wed, 22 Jul 2009 13:30:28 -0500
From: Anthony Liguori <aliguori@us.ibm.com>
MIME-Version: 1.0
References: <20090722141519.2c142274@doriath> <4A675360.9030808@us.ibm.com>
	<20090722151018.71dc04ec@doriath> <4A6757F5.5060909@us.ibm.com>
	<20090722183554.GT4019@poweredge.glommer>
In-Reply-To: <20090722183554.GT4019@poweredge.glommer>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Re: Build currently broken
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: Glauber Costa <glommer@redhat.com>
Cc: qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>

Glauber Costa wrote:
> On Wed, Jul 22, 2009 at 01:18:29PM -0500, Anthony Liguori wrote:
>   
>> Luiz Capitulino wrote:
>>     
>>>  In QEMU you mean?
>>>
>>>  The first commit introducing it seems to be
>>> e22a25c9361c44995c9241c24df0e1e2c47a56c8 , but I have no idea
>>> on how this macro and its code are being used.
>>>   
>>>       
>> No, I was asking when it was introduced in KVM.  We have a minimal set  
>> of capabilities that we require.  It looks like KVM_CAP_SET_GUEST_DEBUG  
>> arrived shortly after KVM_CAP_DESTROY_MEMORY_REGION which is our current  
>> minimum.
>>     
> How will this minimum change if we start backporting things like memory aliasing
> broken for qemu?
>   

Good question.  I don't know.  I really hate to have all of these #ifdef 
KVM_CAPs all over the place though.

Maybe we should re-examine pulling in kvm header files.

-- 
Regards,

Anthony Liguori