From: Ingo Molnar <mingo@elte.hu>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] tracing/function-graph-tracer: prevent from hrtimer interrupt infinite loop
Date: Sun, 21 Dec 2008 11:12:26 +0100 [thread overview]
Message-ID: <20081221101226.GA6021@elte.hu> (raw)
In-Reply-To: <20081221100047.GA31074@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> btw., a graph-tracer buglet i noticed:
another thing. I turned off all the options that come ahead of the 'meat'
of the trace data:
# cat /debug/tracing/trace_options
print-parent nosym-offset nosym-addr noverbose noraw nohex nobin noblock
nostacktrace nosched-tree ftrace_printk noftrace_preempt nobranch annotate
nouserstacktrace nosym-userobj printk-msg-only nofuncgraph-overrun
nofuncgraph-cpu nofuncgraph-overhead nofuncgraph-proc
but i still got the 'duration' field printed:
# tracer: function_graph
#
# DURATION FUNCTION CALLS
# | | | | |
0.865 us | }
| alloc_page_vma() {
0.295 us | get_vma_policy();
0.268 us | policy_zonelist();
| __alloc_pages_internal() {
0.257 us | __might_sleep();
| get_page_from_freelist() {
i'd have expected to only see the flow of execution as it happens.
Ingo
next prev parent reply other threads:[~2008-12-21 10:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 1:09 [PATCH v2] tracing/function-graph-tracer: prevent from hrtimer interrupt infinite loop Frederic Weisbecker
2008-12-18 10:34 ` Ingo Molnar
2008-12-18 10:48 ` Thomas Gleixner
2008-12-18 10:56 ` Frédéric Weisbecker
2008-12-18 11:22 ` Ingo Molnar
2008-12-18 21:07 ` Frédéric Weisbecker
2008-12-18 21:16 ` Ingo Molnar
2008-12-18 21:36 ` Frédéric Weisbecker
2008-12-18 21:44 ` Ingo Molnar
2008-12-18 22:00 ` Frédéric Weisbecker
2008-12-21 10:00 ` Ingo Molnar
2008-12-21 10:12 ` Ingo Molnar [this message]
2008-12-21 12:21 ` Frédéric Weisbecker
2008-12-22 10:46 ` Frédéric Weisbecker
2008-12-18 10:51 ` Frédéric Weisbecker
2008-12-18 11:16 ` Ingo Molnar
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=20081221101226.GA6021@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.