From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NeVuz-0005Jp-DE for qemu-devel@nongnu.org; Mon, 08 Feb 2010 10:52:57 -0500 Received: from [199.232.76.173] (port=40046 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NeVuy-0005JX-Ef for qemu-devel@nongnu.org; Mon, 08 Feb 2010 10:52:56 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NeVuw-0003vF-FT for qemu-devel@nongnu.org; Mon, 08 Feb 2010 10:52:56 -0500 Received: from mx1.redhat.com ([209.132.183.28]:6491) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NeVuv-0003tR-Fz for qemu-devel@nongnu.org; Mon, 08 Feb 2010 10:52:53 -0500 Date: Mon, 8 Feb 2010 13:52:26 -0200 From: Marcelo Tosatti Message-ID: <20100208155226.GC2887@amt.cnet> References: <372238c800e0d57815f472502fdf78e53463bbb6.1265232579.git.jan.kiszka@siemens.com> <20100203234929.GA11012@amt.cnet> <4B6A15EE.4050501@web.de> <20100204130038.GA15671@amt.cnet> <4B6AE1E6.9040805@siemens.com> <4B6AEAB8.3030509@siemens.com> <20100204180555.GA3861@amt.cnet> <4B6B179A.3080704@siemens.com> <4B6B194A.90009@siemens.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4B6B194A.90009@siemens.com> Subject: [Qemu-devel] Re: [PATCH 4/4] KVM: Rework of guest debug state writing List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Anthony Liguori , "qemu-devel@nongnu.org" , "kvm@vger.kernel.org" , Avi Kivity On Thu, Feb 04, 2010 at 08:00:26PM +0100, Jan Kiszka wrote: > Jan Kiszka wrote: > > Marcelo Tosatti wrote: > >> > >> Unrelated to this problem, won't put_vcpu_events, which is executed > >> after KVM_SET_GUEST_DEBUG, overwrite any queued debug exceptions? > > > > Good point, SET_GUEST_DEBUG should be last in the writeback for that reason. > > Actually, we no longer need the exception injection via SET_GUEST_DEBUG > now that we have full access via vcpu_events. > So this needs a cleanup, and I'm afraid quite a few cases are broken > ATM with vcpu_events writeback overwriting the reinjected exceptions. Don't see what you mean here. Can you be more explicit? What breakage?