From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Gleb Natapov <gleb@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, jan.kiszka@siemens.com,
joerg.roedel@amd.com
Subject: Re: [patch 1/2] KVM: x86: handle double and triple faults for every exception
Date: Sun, 15 Nov 2009 16:34:55 +0200 [thread overview]
Message-ID: <4B00118F.4080604@redhat.com> (raw)
In-Reply-To: <4B001031.60508@web.de>
On 11/15/2009 04:29 PM, Jan Kiszka wrote:
> Avi Kivity wrote:
>
>> 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.
>>
> Is the hardware doing some queuing in this case?
Gleb has verified by testing, and Intel has confirmed, that the hardware
does not queue, and will in fact lose traps and NMIs in such a case. So
the small hole is actually present in the processor and we're better off
not queueing! I've forgotten about this but Gleb reminded me.
> Would it be overly
> complicated to adopt the real behavior here?
>
Not only would it be difficult, it would also be incorrect.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-11-15 14:34 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
2009-11-15 13:11 ` Avi Kivity
2009-11-15 14:29 ` Jan Kiszka
2009-11-15 14:34 ` Avi Kivity [this message]
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=4B00118F.4080604@redhat.com \
--to=avi@redhat.com \
--cc=gleb@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