From: Jiri Olsa <jolsa@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Dongsheng <yangds.fnst@cn.fujitsu.com>,
Jiri Olsa <jolsa@kernel.org>
Subject: [PATCH 1/6] perf tools: Add missing event for perf sched record.
Date: Mon, 12 May 2014 11:27:08 +0200 [thread overview]
Message-ID: <1399886833-15472-2-git-send-email-jolsa@kernel.org> (raw)
In-Reply-To: <1399886833-15472-1-git-send-email-jolsa@kernel.org>
From: Dongsheng <yangds.fnst@cn.fujitsu.com>
We should record and process sched:sched_wakeup_new event in
perf sched tool, but currently, there is the process function
for it, without recording it in record subcommand.
This patch add -e sched:sched_wakeup_new to perf sched record.
Signed-off-by: Dongsheng <yangds.fnst@cn.fujitsu.com>
Link: http://lkml.kernel.org/r/710c6edd2162b2cea1711443f54de47c0210d9fd.1399273302.git.yangds.fnst@cn.fujitsu.com
Signed-off-by: Jiri Olsa <jolsa@kernel.org>
---
tools/perf/builtin-sched.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/tools/perf/builtin-sched.c b/tools/perf/builtin-sched.c
index d3fb0ed..7eae501 100644
--- a/tools/perf/builtin-sched.c
+++ b/tools/perf/builtin-sched.c
@@ -1635,6 +1635,7 @@ static int __cmd_record(int argc, const char **argv)
"-e", "sched:sched_stat_runtime",
"-e", "sched:sched_process_fork",
"-e", "sched:sched_wakeup",
+ "-e", "sched:sched_wakeup_new",
"-e", "sched:sched_migrate_task",
};
--
1.8.3.1
next prev parent reply other threads:[~2014-05-12 9:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-12 9:27 [GIT PULL 0/6] perf/core improvements and fixes Jiri Olsa
2014-05-12 9:27 ` Jiri Olsa [this message]
2014-05-12 9:27 ` [PATCH 2/6] perf tools: Adapt the TASK_STATE_TO_CHAR_STR to new value in kernel space Jiri Olsa
2014-05-12 9:27 ` [PATCH 3/6] perf tools: Clarify the output of perf sched map Jiri Olsa
2014-05-12 9:27 ` [PATCH 4/6] perf record: Propagate exit status of a command line workload Jiri Olsa
2014-05-12 9:27 ` [PATCH 5/6] perf tools: Get rid of on_exit() feature test Jiri Olsa
2014-05-12 9:27 ` [PATCH 6/6] perf tools: Use tid for finding thread Jiri Olsa
2014-05-12 15:59 ` [GIT PULL 0/6] perf/core improvements and fixes 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=1399886833-15472-2-git-send-email-jolsa@kernel.org \
--to=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=yangds.fnst@cn.fujitsu.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.