From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-devel] [RFC][PATCH 3/4] kvm-vmx: KVM_EXIT_DEBUG on #BP exceptions Date: Thu, 22 May 2008 17:31:11 +0300 Message-ID: <483583AF.8050402@qumranet.com> References: <482D9198.7040801@web.de> <482DAFFD.8060500@web.de> <4834474B.7030600@qumranet.com> <483575C2.1040303@web.de> <48357BE8.5090104@qumranet.com> <48358230.1000407@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]:51108 "EHLO il.qumranet.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751597AbYEVObN (ORCPT ); Thu, 22 May 2008 10:31:13 -0400 In-Reply-To: <48358230.1000407@web.de> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > /me is still trying to find explicit statements in the Intel docs about > what happens to the TF flag when the CPU enters an interrupt or an > exception handler. This influences how single stepping guests can be > realized, specifically when trying to step into guest's int3 handling... > > It's cleared. -- error compiling committee.c: too many arguments to function