Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1320718
| From | Steven Rostedt <rostedt@goodmis.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [RFC][BUG] tracer: Fails to work |
| Date | 2016-01-28 15:20 +0100 |
| Message-ID | <qVVAu-4Ce-7@gated-at.bofh.it> (permalink) |
| References | <qVPOq-x3-5@gated-at.bofh.it> <qVUXM-43r-17@gated-at.bofh.it> <qVVh9-4b8-29@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 28 Jan 2016 14:57:33 +0100 Peter Zijlstra <peterz@infradead.org> wrote: > On Thu, Jan 28, 2016 at 01:38:00PM +0000, Mathieu Desnoyers wrote: > > > Thoughts ? > > So ideally dumping the trace data would not depend on any of that, > because I can break it all :-) > > Not being able to access the trace data completely and utterly defeats > the purpose of having a tracer in the first place. > The solution is to use trace_pipe. That's for live tracing (or in this case, tracing when the system gets corrupted). I may update the tracing documentation to note this. The trace file preserves the data it reads, and disables the ring buffer before reading it to keep the iterator from being corrupted. But that requires a somewhat working system (not a CPU being stuck). Hence, use trace_pipe for your debugging. The only thing you'll lose is the header that trace provides. -- Steve
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[RFC][BUG] tracer: Fails to work Peter Zijlstra <peterz@infradead.org> - 2016-01-28 09:10 +0100
Re: [RFC][BUG] tracer: Fails to work Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-01-28 14:40 +0100
Re: [RFC][BUG] tracer: Fails to work Peter Zijlstra <peterz@infradead.org> - 2016-01-28 15:00 +0100
Re: [RFC][BUG] tracer: Fails to work Steven Rostedt <rostedt@goodmis.org> - 2016-01-28 15:20 +0100
Re: [RFC][BUG] tracer: Fails to work Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-01-28 15:40 +0100
Re: [RFC][BUG] tracer: Fails to work Peter Zijlstra <peterz@infradead.org> - 2016-01-28 15:50 +0100
Re: [RFC][BUG] tracer: Fails to work Mathieu Desnoyers <mathieu.desnoyers@efficios.com> - 2016-01-28 16:00 +0100
Re: [RFC][BUG] tracer: Fails to work Peter Zijlstra <peterz@infradead.org> - 2016-01-28 16:40 +0100
Re: [RFC][BUG] tracer: Fails to work Steven Rostedt <rostedt@goodmis.org> - 2016-01-28 17:00 +0100
csiph-web