All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
	"x86@kernel.org" <x86@kernel.org>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Rik van Riel <riel@surriel.com>,
	"Yu, Yu-cheng" <yu-cheng.yu@intel.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v3 0/2] x86/fault: Further improve #PF oops messages
Date: Thu, 28 Feb 2019 07:44:33 -0800	[thread overview]
Message-ID: <20190228154433.GB6166@linux.intel.com> (raw)
In-Reply-To: <20181221213657.27628-1-sean.j.christopherson@intel.com>

High latency ping.  These still apply as-is.

On Fri, Dec 21, 2018 at 01:36:55PM -0800, Sean Christopherson wrote:
> Rework the messages printed for #PF oopses to display more detailed
> information about the fault in human readable form and to avoid
> conflicting messages and/or statements that may not always be accurate.
> 
> v3:
>   - Prepend a patch to reword the initial BUG message
>   - Add sample output in the changelogs
>   - Swap the order of the #PF lines.  For most cases the three main lines
>     show up in reverse fir-tree ordering and the cause of the fault is
>     easy to pick out since it's the last thing highlighted by pr_alert
>     (excepting when dumping the IDT, GDT, etc...).
> 
> v2:
>   - Explicitly call out protection keys violations
>   - "Slightly" reword the changelog
> 
> v1: https://lkml.kernel.org/r/20181207195223.23968-1-sean.j.christopherson@intel.com
> v2: https://lkml.kernel.org/r/20181207184423.1962-1-sean.j.christopherson@intel.com
> 
> Sean Christopherson (2):
>   x86/fault: Reword initial BUG message for unhandled page faults
>   x86/fault: Decode and print #PF oops in human readable form
> 
>  arch/x86/mm/fault.c | 51 +++++++++++++++------------------------------
>  1 file changed, 17 insertions(+), 34 deletions(-)
> 
> -- 
> 2.19.2
> 

      parent reply	other threads:[~2019-02-28 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-21 21:36 [PATCH v3 0/2] x86/fault: Further improve #PF oops messages Sean Christopherson
2018-12-21 21:36 ` [PATCH v3 1/2] x86/fault: Reword initial BUG message for unhandled page faults Sean Christopherson
2019-04-19 18:35   ` [tip:x86/mm] " tip-bot for Sean Christopherson
2018-12-21 21:36 ` [PATCH v3 2/2] x86/fault: Decode and print #PF oops in human readable form Sean Christopherson
2019-04-19 18:35   ` [tip:x86/mm] " tip-bot for Sean Christopherson
2019-04-21 18:35     ` Borislav Petkov
2019-04-21 18:52       ` [tip:x86/mm] x86/fault: Make fault messages more succinct tip-bot for Borislav Petkov
2019-04-29 13:58   ` [PATCH v3 2/2] x86/fault: Decode and print #PF oops in human readable form Dmitry Vyukov
2019-04-29 14:14     ` Borislav Petkov
2019-02-28 15:44 ` Sean Christopherson [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=20190228154433.GB6166@linux.intel.com \
    --to=sean.j.christopherson@intel.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=riel@surriel.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    --cc=yu-cheng.yu@intel.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 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.