mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: byungchul.park@lge.com
To: rostedt@goodmis.org
Cc: mingo@redhat.com, linux-kernel@vger.kernel.org,
	seungho1.park@lge.com, jolsa@redhat.com,
	Byungchul Park <byungchul.park@lge.com>
Subject: [PATCH v4 0/3] tracing: signaling large duration and delay
Date: Tue, 18 Nov 2014 14:57:23 +0900	[thread overview]
Message-ID: <1416290246-882-1-git-send-email-byungchul.park@lge.com> (raw)

From: Byungchul Park <byungchul.park@lge.com>

Changes since v3
* re-position define macro and undef explicitly
* enhance readablity

Changes since v2
* use inline function instead of macro
* enhance readablity

Changes since v1
* update Document/trace/ftrace.txt
* seperate the implementation as a macro
* apply the implementation to delay printing, too

Hello.

When I analysis the exit_mm() function to find out the reason why the
function spends much time occasionally, this patch was very useful.
I thought this patch cannot be useful only for me, but can be also
useful for anybody who want to be signaled for very large function
execution time, so I decided to submit this patchset.

Nobody who have such a demand? :)

Thanks,
Byungchul.

Byungchul Park (3):
  tracing, function_graph: fix micro seconds notation in comment
  tracing, function_graph: add additional marks to signal very large
    function execution time
  tracing: add additional marks to signal very large delay

 Documentation/trace/ftrace.txt       |   10 +++++++---
 kernel/trace/trace.h                 |   21 +++++++++++++++++++++
 kernel/trace/trace_functions_graph.c |   31 +++++++++++++++++++++----------
 kernel/trace/trace_output.c          |   23 ++++++++++++++++++-----
 4 files changed, 67 insertions(+), 18 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2014-11-18  5:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18  5:57 byungchul.park [this message]
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
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=1416290246-882-1-git-send-email-byungchul.park@lge.com \
    --to=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®