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 v5 2/2] tracing: add additional marks to signal very large time
Date: Thu, 20 Nov 2014 15:05:43 +0900 [thread overview]
Message-ID: <87ioiapft4.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20141119200604.6b57266d@gandalf.local.home> (Steven Rostedt's message of "Wed, 19 Nov 2014 20:06:04 -0500")
Hi Steve and Byungchul,
On Wed, 19 Nov 2014 20:06:04 -0500, Steven Rostedt wrote:
> On Thu, 20 Nov 2014 09:15:35 +0900
> byungchul.park@lge.com wrote:
>> -static unsigned long preempt_mark_thresh_us = 100;
>> +#undef MARK
>> +#define MARK(v, s) {.val = v, .sym = s}
>> +/* trace overhead mark */
>> +static const struct trace_mark {
>> + unsigned long long val; /* unit: nsec */
>> + char sym;
>> +} mark[] = {
>> + MARK(1000000000ULL , '$'), /* 1 sec */
>> + MARK(1000000ULL , '#'), /* 1000 usecs */
>> + MARK(100000ULL , '!'), /* 100 usecs */
>> + MARK(10000ULL , '+'), /* 10 usecs */
>> + MARK(0ULL , ' '), /* 0 usecs */
>> +};
>> +#undef MARK
>> +
>> +char trace_find_mark(unsigned long long d)
>> +{
>> + int i;
>> + int size = ARRAY_SIZE(mark);
>> +
>> + for (i = 0; i < size; i++) {
>> + if (d >= mark[i].val)
>> + break;
>> + }
>> +
>> + return (i == size)? ' ' : mark[i].sym;
>
> Change this to:
>
> /* The break from loop must have been hit */
> if (WARN_ON_ONCE(i == size))
> return ' ';
I think it's impossible since it's always true that 'd >= 0'.
Thanks,
Namhyung
>
> return mark[i].sym;
>
> -- Steve
>
>
>> +}
>>
>> static int
>> lat_print_timestamp(struct trace_iterator *iter, u64 next_ts)
>> @@ -506,8 +532,7 @@ lat_print_timestamp(struct trace_iterator *iter, u64 next_ts)
>> return trace_seq_printf(
>> s, " %4lldus%c: ",
>> abs_ts,
>> - rel_ts > preempt_mark_thresh_us ? '!' :
>> - rel_ts > 1 ? '+' : ' ');
>> + trace_find_mark(rel_ts * NSEC_PER_USEC));
>> } else { /* !verbose && !in_ns */
>> return trace_seq_printf(s, " %4lld: ", abs_ts);
>> }
>> @@ -692,7 +717,7 @@ int register_ftrace_event(struct trace_event *event)
>> goto out;
>>
>> } else {
>> -
>> +
>> event->type = next_event_type++;
>> list = &ftrace_event_list;
>> }
next prev parent reply other threads:[~2014-11-20 6:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 0:15 [PATCH v5 0/2] tracing: signaling large duration and delay byungchul.park
2014-11-20 0:15 ` [PATCH v5 1/2] tracing, function_graph: fix micro seconds notation in comment byungchul.park
2014-11-20 0:50 ` Steven Rostedt
2014-11-20 0:15 ` [PATCH v5 2/2] tracing: add additional marks to signal very large time byungchul.park
2014-11-20 1:06 ` Steven Rostedt
2014-11-20 6:05 ` Namhyung Kim [this message]
2014-11-20 6:38 ` Byungchul Park
2014-11-20 13:49 ` Steven Rostedt
2014-11-20 13:46 ` 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=87ioiapft4.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 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.