public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <compudj@krystal.dyndns.org>
To: "Stone, Joshua I" <joshua.i.stone@intel.com>,
	  Tom Zanussi <zanussi@us.ibm.com>,
	michel.dagenais@polymtl.ca
Cc: systemtap@sources.redhat.com
Subject: Re: double fault -> PAGE_KERNEL flagged memory
Date: Tue, 22 Nov 2005 15:17:00 -0000	[thread overview]
Message-ID: <20051122151708.GA27520@Krystal> (raw)
In-Reply-To: <20051122140021.GA3907@Krystal>

* Mathieu Desnoyers (compudj@krystal.dyndns.org) wrote:

(talking about causes of a double fault in a Linux Kernel)

[...]
> 
> The same could apply to unaligned memory access.
> 
[...]

Sorry to reply to myself, but this isn't true in the Linux Kernel. The CPU
EFLAG Alignment Check is never activated in the Linux Kernel code. Furthermore,
alignment check exceptions never generate a double fault, as they are "benign
exceptions".

It still apply to page faults :

(from IA32 Intel Architecture Software Developer's Manual p. 6-14 vol.1)

#DF Double Fault

Source :

Any instruction that can generate an exception, an NMI or an INTR.

Well, not "any". For details, see table at vol. 3, p 5-38, same reference. In
fact, NMI and INTR seems to never generate a double fault.

Causes of a double fault :

Divide error, invalid TSS, segment not present, stack fault, general protection
nested on a page fault.

Page fault nested on another page fault.

Divide error, invalid TSS, segment not present, stack fault, general protection
nested on
divide error, invalid TSS, segment not present, stack fault, general protection.

In the other cases, the exceptions are handled serially.


Mathieu


OpenPGP public key:              http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

  parent reply	other threads:[~2005-11-22 15:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-22  1:12 double fault Stone, Joshua I
2005-11-22  1:25 ` Roland McGrath
2005-11-22  9:29 ` Richard J Moore
2005-11-22 14:00 ` double fault -> PAGE_KERNEL flagged memory Mathieu Desnoyers
2005-11-22 15:12   ` Tom Zanussi
2005-11-22 15:24     ` Mathieu Desnoyers
2005-11-22 16:52       ` Tom Zanussi
2005-11-22 18:59         ` Mathieu Desnoyers
2005-11-23 15:13           ` Tom Zanussi
2005-11-23 17:53             ` Mathieu Desnoyers
2005-11-23 20:16               ` Tom Zanussi
2005-11-23 21:00                 ` Frank Ch. Eigler
2005-11-23 21:51                   ` Roland McGrath
2005-11-23 21:56                     ` Mathieu Desnoyers
2005-11-23 22:34                       ` Roland McGrath
2005-11-23 22:44                         ` Mathieu Desnoyers
2005-11-23 23:20                         ` Tom Zanussi
2005-11-24 18:10                         ` Frank Ch. Eigler
2005-11-24 22:09                           ` Roland McGrath
2005-11-23 22:18                   ` Tom Zanussi
2005-11-23 22:25                     ` Frank Ch. Eigler
2005-11-23 23:21                 ` Mathieu Desnoyers
2005-11-22 15:17   ` Mathieu Desnoyers [this message]
2005-11-22 15:42   ` Frank Ch. Eigler
2005-11-22 16:01     ` Mathieu Desnoyers
2005-11-23  8:34 ` double fault Martin Hunt
2005-11-23 17:21   ` Mathieu Desnoyers
2005-11-23 17:54     ` Martin Hunt
2005-11-23 18:09       ` Mathieu Desnoyers

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=20051122151708.GA27520@Krystal \
    --to=compudj@krystal.dyndns.org \
    --cc=joshua.i.stone@intel.com \
    --cc=michel.dagenais@polymtl.ca \
    --cc=systemtap@sources.redhat.com \
    --cc=zanussi@us.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).