From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-devel] [RFC][PATCH 2/4] kvm: Arch-specifc KVM_EXIT_DEBUG payload Date: Thu, 22 May 2008 17:35:50 +0300 Message-ID: <483584C6.6080506@qumranet.com> References: <482D9198.7040801@web.de> <482DAFF6.3050403@web.de> <48344820.60103@qumranet.com> <4835782F.60804@web.de> <48357C4D.9070400@qumranet.com> <483583EF.1010907@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-devel , Hollis Blanchard To: Jan Kiszka Return-path: Received: from bzq-179-150-194.static.bezeqint.net ([212.179.150.194]:52434 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751439AbYEVOfx (ORCPT ); Thu, 22 May 2008 10:35:53 -0400 In-Reply-To: <483583EF.1010907@web.de> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > Well, might be useful. But then we would also have to teach this support > to the gdb remote protocol and the gdb frontend, because neither of both > seems to make use of it yet. And do other archs have it as well? If at > all, I guess the way this is realized there varies a lot, and thus > abstracting it is the real problem. > > However, we can keep it in mind for the time the basic feature set works > perfectly. :) > Right, no need to implement it now. But you can reserve some bytes in the ioctl argument. -- error compiling committee.c: too many arguments to function