From mboxrd@z Thu Jan  1 00:00:00 1970
From: Avi Kivity <avi@qumranet.com>
Subject: Re: [kvm-devel] [RFC][PATCH 3/4] kvm-vmx: KVM_EXIT_DEBUG on #BP	exceptions
Date: Wed, 21 May 2008 19:01:15 +0300
Message-ID: <4834474B.7030600@qumranet.com>
References: <482D9198.7040801@web.de> <482DAFFD.8060500@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: kvm-devel <kvm@vger.kernel.org>,
	Hollis Blanchard <hollisb@us.ibm.com>
To: Jan Kiszka <jan.kiszka@web.de>
Return-path: <kvm-owner@vger.kernel.org>
In-Reply-To: <482DAFFD.8060500@web.de>
Sender: kvm-owner@vger.kernel.org
List-ID: <kvm.vger.kernel.org>

Jan Kiszka wrote:
> In order to allow the gdbstub of QEMU to push (soft) breakpoint handling
> completely into the gdb frontend, this patch enables guest exits also
> for #BP exceptions - in case guest debugging was turned on.
>
> Along this enhancement, this patch also fixes the flag manipulation for
> the singlestep mode.
>   

Suppose userspace determines the exception is due to a guest 
breakpoint.  How does it inject the debug exception?

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