LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: x86: Add the "print code before the trapping instruction" feature to 64 bit
Date: Mon, 14 Jan 2008 09:50:27 +0100	[thread overview]
Message-ID: <20080114085026.GA26367@elte.hu> (raw)
In-Reply-To: <4786780F.90302@redhat.com>


* Chuck Ebbert <cebbert@redhat.com> wrote:

> > Subject: x86: Add the "print code before the trapping instruction" feature to 64 bit
> > From: Arjan van de Ven <arjan@linux.intel.com>
> > 
> > The 32 bit x86 tree has a very useful feature that prints the Code: 
> > line for the code even before the trapping instrution (and the start 
> > of the trapping instruction is then denoted with a <>). 
> > Unfortunately, the 64 bit x86 tree does not yet have this feature, 
> > making diagnosing backtraces harder than needed.
> > 
> > This patch adds this feature in the same was as the 32 bit tree has 
> > (including the same kernel boot parameter), and including a bugfix 
> > to make the code use probe_kernel_address() rarther than a buggy 
> > (deadlocking) __get_user.
> > 
> 
> If this get accepted I can stop ignoring x86_64 oops reports...

yep - all of Arjan's patches are in x86.git. (right now with a merge 
target of v2.6.25)

	Ingo

      reply	other threads:[~2008-01-14  8:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10 16:47 x86: Add the "print code before the trapping instruction" feature to 64 bit Arjan van de Ven
2008-01-10 19:54 ` Chuck Ebbert
2008-01-14  8:50   ` Ingo Molnar [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=20080114085026.GA26367@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).