public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Christoph Hellwig <hch@infradead.org>,
	Lai Jiangshan <laijs@cn.fujitsu.com>,
	Dave Anderson <anderson@redhat.com>,
	crash-utility@redhat.com, Ingo Molnar <mingo@elte.hu>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	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>,
	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, 03 Aug 2009 16:04:30 -0500	[thread overview]
Message-ID: <4A7750DE.3090501@windriver.com> (raw)
In-Reply-To: <87ljm0tyb7.fsf@basil.nowhere.org>

Andi Kleen wrote:
> Jason Wessel <jason.wessel@windriver.com> writes:
>   
>> In no particular order, tracing, kernel probes, profiling data display,
>> kdump, disassembly and kernel mode setting were some of the pieces that
>> are on the wish list for integration with the kdb prototype.  Kernel
>> mode setting is presently the highest priority on the wish list for a
>> new feature.
>>     
>
> I suspect for a lot of people the highest priority issue would be
> a polled USB keybord driver. Or do you plan to use the one from
> old kdb (iirc it was pretty crufty)
>
>   

There is a working usb keyboard driver in the kdb prototype.  I am not
certain about the degree to which the driver is robust or not.  I had
added a uhci implementation to the kdb prototype because I had a uhci
keyboard which didn't work at all.  The kdb usb code is quite complex
and not necessarily the long term approach to the problem.  That means
that if you have a uchi, ehci or ohci port on your board and typical usb
keyboard it has at least the possibility of working.

All these sorts of issues require a good deal of testing and review, 
right now it is at the stage where somethings work, and having other
people contribute to the project would be highly desired.

Jason.

  reply	other threads:[~2009-08-03 21:07 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
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 [this message]
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=4A7750DE.3090501@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=acme@ghostprotocols.net \
    --cc=akpm@linux-foundation.org \
    --cc=anderson@redhat.com \
    --cc=andi@firstfloor.org \
    --cc=clark.williams@gmail.com \
    --cc=crash-utility@redhat.com \
    --cc=fche@redhat.com \
    --cc=fweisbec@gmail.com \
    --cc=hch@infradead.org \
    --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