xfs
[Top] [All Lists]

Re: TAKE 988255 - fix instant oops with tracing enabled

To: Timothy Shimmin <tes@xxxxxxx>
Subject: Re: TAKE 988255 - fix instant oops with tracing enabled
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 14 Oct 2008 08:56:50 -0400
Cc: xfs@xxxxxxxxxxx
In-reply-to: <48F43838.9040606@xxxxxxx>
References: <20081014011747.AC14E58FA1E9@xxxxxxxxxxxxxxxxxxxxxxx> <20081014020556.GH10716@disturbed> <48F42F12.1010409@xxxxxxx> <20081014054103.GK10716@disturbed> <48F43838.9040606@xxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Tue, Oct 14, 2008 at 05:12:08PM +1100, Timothy Shimmin wrote:
> OOI, can anyone comment on any suggestions for other tracing mechanisms.
> I recall Christoph mentioning something in the past but it wasn't
> ready yet or something???.
> I'd really like to be able to access tracing output via proc
> instead of just within kdb,
> as I have used in the past with Greg Banks qtrace patches.

Yah, I've been working on doing that and wire it up with trace_mark.
I'll move it up on my TODO list a little..

<Prev in Thread] Current Thread [Next in Thread>