public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org, jan.kiszka@siemens.com,
	joerg.roedel@amd.com, Jan Kiszka <jan.kiszka@web.de>
Subject: Re: [patch 1/2] KVM: x86: handle double and triple faults for every exception
Date: Sun, 15 Nov 2009 14:51:46 +0200	[thread overview]
Message-ID: <20091115125146.GF7392@redhat.com> (raw)
In-Reply-To: <4AFFF716.5000708@redhat.com>

On Sun, Nov 15, 2009 at 02:41:58PM +0200, Avi Kivity wrote:
> On 11/12/2009 02:26 PM, Gleb Natapov wrote:
> >>
> >>-	if (vcpu->arch.exception.pending) {
> >>-		switch(vcpu->arch.exception.nr) {
> >>-		case DF_VECTOR:
> >>-			/* triple fault ->  shutdown */
> >>-			set_bit(KVM_REQ_TRIPLE_FAULT,&vcpu->requests);
> >>-			return;
> >>-		case PF_VECTOR:
> >>-			vcpu->arch.exception.nr = DF_VECTOR;
> >>-			vcpu->arch.exception.error_code = 0;
> >>-			return;
> >>-		default:
> >>-			/* replace previous exception with a new one in a hope
> >>-			   that instruction re-execution will regenerate lost
> >>-			   exception */
> >>-			vcpu->arch.exception.pending = false;
> >>-			break;
> >When exceptions are handled serially previous exception have to be
> >replaced by new one. Think about #PF during #DE. #PF should be handled first
> >before #DE can proceed.
> 
> "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.

--
			Gleb.

  reply	other threads:[~2009-11-15 12:51 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-11 19:29 [patch 0/2] Handle multiple exceptions (fixes Win2003 reboot by triple fault) Marcelo Tosatti
2009-11-11 19:29 ` [patch 1/2] KVM: x86: handle double and triple faults for every exception Marcelo Tosatti
2009-11-11 20:07   ` Jan Kiszka
2009-11-11 20:41     ` Marcelo Tosatti
2009-11-11 21:02       ` Jan Kiszka
2009-11-11 21:40         ` Marcelo Tosatti
2009-11-15 12:30           ` Avi Kivity
2009-11-12 12:26   ` Gleb Natapov
2009-11-15 12:41     ` Avi Kivity
2009-11-15 12:51       ` Gleb Natapov [this message]
2009-11-15 13:11         ` Avi Kivity
2009-11-15 14:29           ` Jan Kiszka
2009-11-15 14:34             ` Avi Kivity
2009-11-15 14:36               ` Jan Kiszka
2009-11-11 19:29 ` [patch 2/2] KVM: x86: raise TSS exception for NULL CS and SS segments Marcelo Tosatti
2009-11-12 12:21 ` [patch 0/2] Handle multiple exceptions (fixes Win2003 reboot by triple fault) Gleb Natapov
2009-11-12 12:41   ` Jan Kiszka
2009-11-12 13:05     ` Gleb Natapov
2009-11-15 12:54       ` Avi Kivity
2009-11-19 15:54         ` Gleb Natapov
2009-11-20 15:55           ` Ryan Harper
2009-11-23 16:52           ` Marcelo Tosatti
2009-11-25  9:55           ` Avi Kivity
2009-11-25 13:03           ` Marcelo Tosatti
2009-11-12 16:07   ` Marcelo Tosatti
2009-11-12 18:03     ` Gleb Natapov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091115125146.GF7392@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jan.kiszka@web.de \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox