From: Andi Kleen <ak@suse.de>
To: richardj_moore@uk.ibm.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why is double_fault serviced by a trap gate?
Date: Thu, 7 Dec 2000 17:13:53 +0100 [thread overview]
Message-ID: <20001207171353.A28798@gruyere.muc.suse.de> (raw)
In-Reply-To: <802569AE.00588787.00@d06mta06.portsmouth.uk.ibm.com>
In-Reply-To: <802569AE.00588787.00@d06mta06.portsmouth.uk.ibm.com>; from richardj_moore@uk.ibm.com on Thu, Dec 07, 2000 at 04:04:21PM +0000
On Thu, Dec 07, 2000 at 04:04:21PM +0000, richardj_moore@uk.ibm.com wrote:
>
>
> Why is double_fault serviced by a trap gate? The problem with this is that
> any double-fault caused by a stack-fault, which is the usual reason,
> becomes a triple-fault. And a triple-fault results in a processor reset or
> shutdown making the fault damn near impossible to get any information on.
>
> Oughtn't the double-fault exception handler be serviced by a task gate? And
> similarly the NMI handler in case the NMI is on the current stack page
> frame?
Sounds like a good idea, when you can afford a few K for a special
NMI/double fault stack. On x86-64 it is planned to do that.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-07 16:44 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 16:04 richardj_moore
2000-12-07 16:13 ` Andi Kleen [this message]
2000-12-07 16:31 ` Richard B. Johnson
2000-12-07 16:55 ` Maciej W. Rozycki
2000-12-07 18:05 ` Andi Kleen
2000-12-07 18:11 ` Maciej W. Rozycki
2000-12-07 18:29 ` Andi Kleen
2000-12-07 18:47 ` Maciej W. Rozycki
2000-12-07 18:13 Petr Vandrovec
2000-12-07 18:04 ` Maciej W. Rozycki
2000-12-07 20:20 Petr Vandrovec
2000-12-07 19:38 ` Maciej W. Rozycki
2000-12-07 21:09 richardj_moore
2000-12-07 21:44 ` Richard B. Johnson
2000-12-07 22:36 ` Brian Gerst
2000-12-08 1:36 ` Richard B. Johnson
2000-12-08 11:44 ` Maciej W. Rozycki
2000-12-07 22:47 ` Keith Owens
2000-12-08 11:30 ` Maciej W. Rozycki
2000-12-07 23:01 Petr Vandrovec
2000-12-07 23:03 richardj_moore
2000-12-07 23:08 richardj_moore
2000-12-08 8:37 richardj_moore
2000-12-08 12:58 ` Richard B. Johnson
2000-12-08 22:34 ` Keith Owens
2000-12-08 20:31 ` Mikulas Patocka
2000-12-08 13:18 richardj_moore
2000-12-08 16:34 richardj_moore
2000-12-08 16:52 ` Richard B. Johnson
2000-12-08 20:48 richardj_moore
2000-12-09 23:46 richardj_moore
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=20001207171353.A28798@gruyere.muc.suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richardj_moore@uk.ibm.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
all inboxes | Powered by JetHome®