public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Hui Zhu <teawater@gmail.com>
Cc: Arjan van de Ven <arjan@infradead.org>,
	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: Tue, 05 Jan 2010 18:20:23 +0900	[thread overview]
Message-ID: <4B430457.5020906@kernel.org> (raw)
In-Reply-To: <daef60381001050104u5d4adf11k16bec2406501fbd2@mail.gmail.com>

Hello,

On 01/05/2010 06:04 PM, Hui Zhu wrote:
> I agree with read the current stack message is better.
> 
> About the extending, I have some question with it:
> 1.  markup_oops.pl have itself idea, it try use dmesg| markup_oops.pl
> show what happen to usr.  This is different with s2c.
> I am not sure people like it have other function with it.  Too much
> part of this file need to be change.  It need rewrite, just the oops
> message parse part can be keep.

Yeah, I think you'll need to refactor it and share only the parsing
frontend.  Just adding a switch (-m or whatever) which puts it into
machine-friendly translator mode should do the trick.

> 2.  I use perl to work in a long time before, I know it good at parse
> the text, but I am not sure it good at handle struct like:

You don't need to handle the data structure at all.  Just make it
parse the dmesg and output machine-friendly formatted output which can
be processed by s2c.  ie. just make it do the reformatting.

> Even if what happen, I will keep a c s2c with myself.  :)

That will be sad.  I really want it too.  :-)

Thanks.

-- 
tejun

  reply	other threads:[~2010-01-05  9:16 UTC|newest]

Thread overview: 22+ 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 16:03 ` Russell King - ARM Linux
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 17:10         ` Russell King - ARM Linux
2010-01-03 17:18           ` Hui Zhu
2010-01-03 17:37             ` Hui Zhu
2010-01-03 17:26         ` Arjan van de Ven
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
2010-01-03 23:24         ` Tejun Heo
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:20               ` Tejun Heo [this message]
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=4B430457.5020906@kernel.org \
    --to=tj@kernel.org \
    --cc=Paul.Gortmaker@windriver.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.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=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