Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Tejun Heo <tj@kernel.org>
Cc: Hui Zhu <teawater@gmail.com>,
	Russell King <linux@arm.linux.org.uk>,
	saeed bishara <saeed.bishara@gmail.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Nicolas Pitre <nico@fluxnic.net>,
	Ralf Baechle <ralf@linux-mips.org>,
	David Daney <ddaney@caviumnetworks.com>,
	Tomaso Paoletti <tpaoletti@caviumnetworks.com>,
	Chris Dearman <chris@mips.com>,
	Paul Gortmaker <Paul.Gortmaker@windriver.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Frederic Weisbecker <fweisbec@gmail.com>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Brian Gerst <brgerst@gmail.com>,
	Rusty Russell <rusty@rustcorp.com.au>,
	Andrew Morton <akpm@linux-foundation.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Greg Kroah-Hartman <gregkh@suse.de>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
	Coly Li <coly.li@suse.de>
Subject: Re: [PATCH] stack2core: show stack message and convert it to core file   when kernel die
Date: Sun, 3 Jan 2010 15:14:06 -0800	[thread overview]
Message-ID: <20100103151406.20228c3a@infradead.org> (raw)
In-Reply-To: <4B412341.2010002@kernel.org>

On Mon, 04 Jan 2010 08:07:45 +0900
Tejun Heo <tj@kernel.org> wrote:

> On 01/04/2010 08:01 AM, Arjan van de Ven wrote:
> > On Mon, 04 Jan 2010 07:49:56 +0900
> > Tejun Heo <tj@kernel.org> wrote:
> >>
> >> If implementing parsing of oops message in C is too awkward
> >> (unsurprising at all), maybe implementing a converter in perl or
> >> python is the easiest way so that it takes the oops message and
> >> puts out well formatted input for the s2c program?
> > 
> > you mean like scripts/markup_oops.pl ?
> 
> Whichever one works but s2c wouldn't require symbol decoding.  Maybe
> we can simply add an option to tell it to just parse the oops and
> output it in machine friendly format.  Oh, also, the patch does add
> new information the module load addresses.  We should be able to add
> those to the oops message in a compact form.

actually one does not need those; you know the start address of the
function already from the current oops output, and since you know the
address of the function within the module as well, you know the start
address of the module.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

  reply	other threads:[~2010-01-03 23:12 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-03 15:05 [PATCH] stack2core: show stack message and convert it to core file when kernel die Hui Zhu
2010-01-03 15:05 ` Hui Zhu
2010-01-03 16:03 ` Russell King - ARM Linux
2010-01-03 16:30   ` Hui Zhu
2010-01-03 16:30     ` Hui Zhu
2010-01-03 16:44     ` Russell King - ARM Linux
2010-01-03 16:55       ` Hui Zhu
2010-01-03 16:55         ` Hui Zhu
2010-01-03 17:10         ` Russell King - ARM Linux
2010-01-03 17:18           ` Hui Zhu
2010-01-03 17:18             ` Hui Zhu
2010-01-03 17:37             ` Hui Zhu
2010-01-03 17:37               ` Hui Zhu
2010-01-03 17:26         ` Arjan van de Ven
2010-01-03 17:26           ` Arjan van de Ven
2010-01-03 17:39           ` Hui Zhu
2010-01-03 17:39             ` Hui Zhu
2010-01-03 17:47             ` Russell King - ARM Linux
2010-01-03 18:32               ` Marek Vasut
2010-01-03 22:49 ` Tejun Heo
2010-01-03 23:01   ` Arjan van de Ven
2010-01-03 23:07     ` Tejun Heo
2010-01-03 23:14       ` Arjan van de Ven [this message]
2010-01-03 23:24         ` Tejun Heo
2010-01-04 16:22         ` Hui Zhu
2010-01-04 16:22           ` Hui Zhu
2010-01-04 23:03           ` Tejun Heo
2010-01-05  9:04             ` Hui Zhu
2010-01-05  9:04               ` Hui Zhu
2010-01-05  9:20               ` Tejun Heo
2010-01-06  7:07                 ` Hui Zhu
2010-01-06  7:07                   ` Hui Zhu

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=20100103151406.20228c3a@infradead.org \
    --to=arjan@infradead.org \
    --cc=Paul.Gortmaker@windriver.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=brgerst@gmail.com \
    --cc=catalin.marinas@arm.com \
    --cc=chris@mips.com \
    --cc=coly.li@suse.de \
    --cc=ddaney@caviumnetworks.com \
    --cc=fweisbec@gmail.com \
    --cc=gregkh@suse.de \
    --cc=hpa@zytor.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mingo@redhat.com \
    --cc=nico@fluxnic.net \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=ralf@linux-mips.org \
    --cc=rostedt@goodmis.org \
    --cc=rusty@rustcorp.com.au \
    --cc=saeed.bishara@gmail.com \
    --cc=teawater@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=tpaoletti@caviumnetworks.com \
    --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