From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: Re: [RFC][BUG] tracer: Fails to work
Date: Thu, 28 Jan 2016 09:18:54 -0500 [thread overview]
Message-ID: <20160128091854.45d0ac2b@gandalf.local.home> (raw)
In-Reply-To: <20160128135733.GQ6356@twins.programming.kicks-ass.net>
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
next prev parent reply other threads:[~2016-01-28 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 8:08 Peter Zijlstra
2016-01-28 13:38 ` Mathieu Desnoyers
2016-01-28 13:57 ` Peter Zijlstra
2016-01-28 14:18 ` Steven Rostedt [this message]
2016-01-28 14:38 ` Mathieu Desnoyers
2016-01-28 14:47 ` Peter Zijlstra
2016-01-28 14:53 ` Mathieu Desnoyers
2016-01-28 15:29 ` Peter Zijlstra
2016-01-28 15:55 ` Steven Rostedt
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=20160128091854.45d0ac2b@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®