From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MTgOr-0003ud-30 for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:18:45 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MTgOl-0003sA-UI for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:18:44 -0400 Received: from [199.232.76.173] (port=54273 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MTgOl-0003s1-Hl for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:18:39 -0400 Received: from e32.co.us.ibm.com ([32.97.110.150]:39590) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MTgOl-0005E9-30 for qemu-devel@nongnu.org; Wed, 22 Jul 2009 14:18:39 -0400 Received: from d03relay04.boulder.ibm.com (d03relay04.boulder.ibm.com [9.17.195.106]) by e32.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n6MIEQGI015756 for ; Wed, 22 Jul 2009 12:14:26 -0600 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by d03relay04.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n6MIIVML225184 for ; Wed, 22 Jul 2009 12:18: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 n6MIIV8g014960 for ; Wed, 22 Jul 2009 12:18:31 -0600 Message-ID: <4A6757F5.5060909@us.ibm.com> Date: Wed, 22 Jul 2009 13:18:29 -0500 From: Anthony Liguori MIME-Version: 1.0 References: <20090722141519.2c142274@doriath> <4A675360.9030808@us.ibm.com> <20090722151018.71dc04ec@doriath> In-Reply-To: <20090722151018.71dc04ec@doriath> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: Build currently broken List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Luiz Capitulino Cc: glommer@redhat.com, qemu-devel@nongnu.org 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. Can you send your patch as a top-level patch? Regards, Anthony Liguori -- Regards, Anthony Liguori