From: Dave Hansen <dave.hansen@linux.intel.com>
To: Andy Lutomirski <luto@kernel.org>, x86@kernel.org
Cc: Borislav Petkov <bp@alien8.de>,
LKML <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>
Subject: Re: [PATCH] x86/fault: Decode page fault OOPSes better
Date: Thu, 6 Sep 2018 10:27:08 -0700 [thread overview]
Message-ID: <8268eb6b-ea83-385f-de5f-e79f4d8a454c@linux.intel.com> (raw)
In-Reply-To: <0a4c64885e9a51705dcc0f49526823ed429e0720.1535773238.git.luto@kernel.org>
On 08/31/2018 08:42 PM, Andy Lutomirski wrote:
> One of Linus' favorite hobbies seems to be looking at OOPSes and
> decoding the error code in his head. This is not one of my favorite
> hobbies :)
I just work around this by having a screenshot of 'enum
x86_pf_error_code' as my desktop background.
I love stuff like this. I'd only ask for more, like in
show_signal_msg() or the page fault tracepoints too.
BTW, I'm feeling rather perturbed that error_code diverges from the
hardware-issued error code for user-mode implicit accesses/buglets. I
really wish captured the "raw" hardware error codes.
prev parent reply other threads:[~2018-09-06 17:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-01 3:42 Andy Lutomirski
2018-09-06 13:32 ` Thomas Gleixner
2018-09-06 17:27 ` Dave Hansen [this message]
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=8268eb6b-ea83-385f-de5f-e79f4d8a454c@linux.intel.com \
--to=dave.hansen@linux.intel.com \
--cc=bp@alien8.de \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome