From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 1/2] KVM: x86: handle double and triple faults for every exception Date: Sun, 15 Nov 2009 15:11:54 +0200 Message-ID: <4AFFFE1A.9090203@redhat.com> References: <20091111192947.348198723@localhost.localdomain> <20091111193837.115825934@localhost.localdomain> <20091112122659.GC7392@redhat.com> <4AFFF716.5000708@redhat.com> <20091115125146.GF7392@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, jan.kiszka@siemens.com, joerg.roedel@amd.com, Jan Kiszka To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:41870 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752753AbZKONLw (ORCPT ); Sun, 15 Nov 2009 08:11:52 -0500 In-Reply-To: <20091115125146.GF7392@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 11/15/2009 02:51 PM, Gleb Natapov wrote: > >> "replacing" exceptions is dangerous in the case of debug exceptions >> and machine checks, since restarting execution won't recover them. >> >> > But not replacing them is not better. No point in re-injecting > exception that causes another exception. > Right, just pointing out there's still a small hole left. Replacing is much better ignoring. -- error compiling committee.c: too many arguments to function