From: Andi Kleen <ak@suse.de>
To: "Jan Beulich" <JBeulich@novell.com>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: DIE_GPF vs. DIE_PAGE_FAULT/DIE_TRAP
Date: Wed, 26 Oct 2005 17:50:44 +0200 [thread overview]
Message-ID: <200510261750.44501.ak@suse.de> (raw)
In-Reply-To: <435FBB1A.76F0.0078.0@novell.com>
On Wednesday 26 October 2005 17:21, Jan Beulich wrote:
> Hmm, then this isn't really useful for a debugger. There ought to be a
> chance to filter exceptions early (i.e. debugger accesses to non-mapped
> memory or non-existing MSRs) and a chance to detect bad faults (note
> that the kernel normal exception recovery mechanism may not be usable
> here because for example page faults first try to service the fault
> before scanning the fixup tables, but a debugger will normally not want
> a page-in to happen behind its back). I thought the latter was what gets
> reported as DIE_OOPS, while the former would be the filtering occasions
> (and I actually took the "grossly misnamed" comment in asm/kdebug.h as
> additional indication for that).
All you want is a hook early in GPF, right? I guess that should be ok.
I can see that it's useful on x86-64 due to the non canonical address
fault resulting in GPFs mess.
Just send a patch.
-Andi
next prev parent reply other threads:[~2005-10-26 15:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 14:44 DIE_GPF vs. DIE_PAGE_FAULT/DIE_TRAP Jan Beulich
2005-10-26 15:01 ` Andi Kleen
2005-10-26 15:21 ` Jan Beulich
2005-10-26 15:50 ` Andi Kleen [this message]
2005-10-26 16:00 ` Jan Beulich
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=200510261750.44501.ak@suse.de \
--to=ak@suse.de \
--cc=JBeulich@novell.com \
--cc=discuss@x86-64.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.