From: Christoph Hellwig <hch@infradead.org>
To: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Dave Anderson <anderson@redhat.com>,
crash-utility@redhat.com, Ingo Molnar <mingo@elte.hu>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
"Luis Claudio R. Goncalves" <lclaudio@uudg.org>,
Clark Williams <clark.williams@gmail.com>,
Jon Masters <jonathan@jonmasters.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Christoph Hellwig <hch@infradead.org>,
Xiao Guangrong <xiaoguangrong@cn.fujitsu.com>,
Zhaolei <zhaolei@cn.fujitsu.com>,
kosaki.motohiro@jp.fujitsu.com, Li Zefan <lizf@cn.fujitsu.com>,
Masami Hiramatsu <mhiramat@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Tom Zanussi <tzanussi@gmail.com>, Jason Baron <jbaron@redhat.com>,
srostedt@redhat.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE][RFC][PATCH] Crash-utility, tracing: enable crash to analyze tracing from core-file (make tracing can act as a flight recorder)
Date: Mon, 3 Aug 2009 11:14:20 -0400 [thread overview]
Message-ID: <20090803151420.GA8712@infradead.org> (raw)
In-Reply-To: <4A76F8A1.30503@cn.fujitsu.com>
On Mon, Aug 03, 2009 at 10:48:01PM +0800, Lai Jiangshan wrote:
>
> We use tracing subsystem very well when kernel is alive.
> But we also want to get help from tracing when kernel is core-dump.
> This patch is for this purpose. It makes tracing can act as a
> flight recorder, we can find what have happen from the events.
Nice! Now the only thing missing is gettind kdb in mainline and a trace
reader in kdb ;-)
Any idea how easy it is to reuse the crash/gdb code for looking at crash
dumps through kgdb?
Btw, the Cc list here seems to be a very strong indicator that we
should have a linux-trace@vger list, I already noticed this for tons
of other tracing patches.
next prev parent reply other threads:[~2009-08-03 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-03 14:48 [ANNOUNCE][RFC][PATCH] Crash-utility, tracing: enable crash to analyze tracing from core-file (make tracing can act as a flight recorder) Lai Jiangshan
2009-08-03 15:14 ` Christoph Hellwig [this message]
2009-08-03 15:21 ` Peter Zijlstra
2009-08-03 19:47 ` Jason Wessel
2009-08-03 20:52 ` Andi Kleen
2009-08-03 21:04 ` Jason Wessel
2009-08-03 21:53 ` Christoph Hellwig
2009-08-03 15:42 ` Peter Zijlstra
2009-08-04 6:52 ` Lai Jiangshan
2009-08-04 10:36 ` Peter Zijlstra
2009-08-04 16:23 ` Steven Rostedt
2009-08-04 16:55 ` Masami Hiramatsu
2009-09-12 4:15 ` [ANNOUNCE][RFC] trace extension module for crash Lai Jiangshan
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=20090803151420.GA8712@infradead.org \
--to=hch@infradead.org \
--cc=acme@ghostprotocols.net \
--cc=akpm@linux-foundation.org \
--cc=anderson@redhat.com \
--cc=clark.williams@gmail.com \
--cc=crash-utility@redhat.com \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=jonathan@jonmasters.org \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=lclaudio@uudg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mhiramat@redhat.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
--cc=tzanussi@gmail.com \
--cc=xiaoguangrong@cn.fujitsu.com \
--cc=zhaolei@cn.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox