From: Namhyung Kim <namhyung@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: byungchul.park@lge.com, mingo@redhat.com,
linux-kernel@vger.kernel.org, seungho1.park@lge.com,
jolsa@redhat.com
Subject: Re: [PATCH v4 3/3] tracing: add additional marks to signal very large delay
Date: Thu, 20 Nov 2014 15:11:19 +0900 [thread overview]
Message-ID: <87egsypfjs.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20141119133515.1caa293e@gandalf.local.home> (Steven Rostedt's message of "Wed, 19 Nov 2014 13:35:15 -0500")
On Wed, 19 Nov 2014 13:35:15 -0500, Steven Rostedt wrote:
> On Tue, 18 Nov 2014 14:57:26 +0900
> byungchul.park@lge.com wrote:
>
>> From: Byungchul Park <byungchul.park@lge.com>
>>
>> Currently, some tracers tracing latency print "!" or "+" just after time
>> to signal overhead, depending on the interval between events. Even it is
>> usually enough to do that, we sometimes need to be signaled for bigger
>> interval than 100 micro seconds.
>>
>> Signed-off-by: Byungchul Park <byungchul.park@lge.com>
>> ---
>> Documentation/trace/ftrace.txt | 8 +++++---
>> kernel/trace/trace_output.c | 23 ++++++++++++++++++-----
>> 2 files changed, 23 insertions(+), 8 deletions(-)
>>
>> diff --git a/Documentation/trace/ftrace.txt b/Documentation/trace/ftrace.txt
>> index f827e2f..64efb3e 100644
>> --- a/Documentation/trace/ftrace.txt
>> +++ b/Documentation/trace/ftrace.txt
>> @@ -680,9 +680,11 @@ The above is mostly meaningful for kernel developers.
>> needs to be fixed to be only relative to the same CPU.
>> The marks are determined by the difference between this
>> current trace and the next trace.
>> - '!' - greater than preempt_mark_thresh (default 100)
>> - '+' - greater than 1 microsecond
>> - ' ' - less than or equal to 1 microsecond.
>> + '$' - greater than 1 second
>> + '#' - greater than 1000 microsecond
>> + '!' - greater than 100 microsecond
>> + '+' - greater than 10 microsecond
I've noticed that it's now changed from 1 msec to 10 msec. Is it okay?
Thanks,
Namhyung
>> + ' ' - less than or equal to 10 microsecond.
>>
>> The rest is the same as the 'trace' file.
next prev parent reply other threads:[~2014-11-20 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 5:57 [PATCH v4 0/3] tracing: signaling large duration and delay byungchul.park
2014-11-18 5:57 ` [PATCH v4 1/3] tracing, function_graph: fix micro seconds notation in comment byungchul.park
2014-11-18 5:57 ` [PATCH v4 2/3] tracing, function_graph: add additional marks to signal very large function execution time byungchul.park
2014-11-18 5:57 ` [PATCH v4 3/3] tracing: add additional marks to signal very large delay byungchul.park
2014-11-19 18:35 ` Steven Rostedt
2014-11-20 0:18 ` Byungchul Park
2014-11-20 6:11 ` Namhyung Kim [this message]
2014-11-20 6:33 ` Byungchul Park
2014-11-20 13:50 ` 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=87egsypfjs.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=byungchul.park@lge.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=seungho1.park@lge.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
all inboxes | Powered by JetHome®