linux-toradex.git/include/trace/events/sched.h, branch v3.4.49

tracing, sched, vfs: Fix 'old_pid' usage in trace_sched_process_exec()

2012-03-31T09:53:22+00:00

1. TRACE_EVENT(sched_process_exec) forgets to actually use the
   old pid argument, it sets ->old_pid = p->pid.

2. search_binary_handler() uses the wrong pid number. tracepoint
   needs the global pid_t from the root namespace, while old_pid
   is the virtual pid number as it seen by the tracer/parent.

With this patch we have two pid_t's in search_binary_handler(),
not really nice. Perhaps we should switch to "struct pid*", but
in this case it would be better to cleanup the current code
first and move the "depth == 0" code outside.

Signed-off-by: Oleg Nesterov 
Cc: David Smith 
Cc: Peter Zijlstra 
Cc: Steven Rostedt 
Cc: Denys Vlasenko 
Link: http://lkml.kernel.org/r/20120330162636.GA4857@redhat.com
Signed-off-by: Ingo Molnar

Merge branch 'perf/urgent' into perf/core

2012-03-05T08:20:08+00:00

Conflicts:
	tools/perf/builtin-record.c
	tools/perf/builtin-top.c
	tools/perf/perf.h
	tools/perf/util/top.h

Merge reason: resolve these cherry-picking conflicts.

Signed-off-by: Ingo Molnar

tracepoint, vfs, sched: Add exec() tracepoint

2012-02-23T08:28:06+00:00

Added a minimal exec tracepoint. Exec is an important major event
in the life of a task, like fork(), clone() or exit(), all of
which we already trace.

[ We also do scheduling re-balancing during exec() - so it's useful
  from a scheduler instrumentation POV as well. ]

If you want to watch a task start up, when it gets exec'ed is a good place
to start.  With the addition of this tracepoint, exec's can be monitored
and better picture of general system activity can be obtained. This
tracepoint will also enable better process life tracking, allowing you to
answer questions like "what process keeps starting up binary X?".

This tracepoint can also be useful in ftrace filtering and trigger
conditions: i.e. starting or stopping filtering when exec is called.

Signed-off-by: David Smith 
Signed-off-by: Peter Zijlstra 
Cc: Steven Rostedt 
Cc: Christoph Hellwig 
Cc: Al Viro 
Cc: Andrew Morton 
Cc: Linus Torvalds 
Link: http://lkml.kernel.org/r/4F314D19.7030504@redhat.com
Signed-off-by: Ingo Molnar

sched/events: Revert trace_sched_stat_sleeptime()

2012-02-22T11:06:55+00:00

Commit 1ac9bc69 ("sched/tracing: Add a new tracepoint for sleeptime")
added a new sched:sched_stat_sleeptime tracepoint.

It's broken: the first sample we get on a task might be bad because
of a stale sleep_start value that wasn't reset at the last task switch
because the tracepoint was not active.

It also breaks the existing schedstat samples due to the side
effects of:

-               se->statistics.sleep_start = 0;
...
-               se->statistics.block_start = 0;

Nor do I see means to fix it without adding overhead to the scheduler
fast path, which I'm not willing to for the sake of redundant
instrumentation.

Most importantly, sleep time information can already be constructed
by tracing context switches and wakeups, and taking the timestamp
difference between the schedule-out, the wakeup and the schedule-in.

Signed-off-by: Peter Zijlstra 
Cc: Andrew Vagin 
Cc: Arnaldo Carvalho de Melo 
Cc: Frederic Weisbecker 
Link: http://lkml.kernel.org/n/tip-pc4c9qhl8q6vg3bs4j6k0rbd@git.kernel.org
Signed-off-by: Ingo Molnar

sched/tracing: Add a new tracepoint for sleeptime

2011-12-23T16:56:17+00:00

If CONFIG_SCHEDSTATS is defined, the kernel maintains
information about how long the task was sleeping or
in the case of iowait, blocking in the kernel before
getting woken up.

This will be useful for sleep time profiling.

Note: this information is only provided for sched_fair.
Other scheduling classes may choose to provide this in
the future.

Note: the delay includes the time spent on the runqueue
as well.

Signed-off-by: Arun Sharma 
Acked-by: Peter Zijlstra 
Cc: Steven Rostedt 
Cc: Mathieu Desnoyers 
Cc: Arnaldo Carvalho de Melo 
Cc: Andrew Vagin 
Cc: Frederic Weisbecker 
Link: http://lkml.kernel.org/r/1324512940-32060-2-git-send-email-asharma@fb.com
Signed-off-by: Ingo Molnar

events, sched: Add tracepoint for accounting blocked time

2011-12-06T07:51:23+00:00

This tracepoint shows how long a task is sleeping in uninterruptible state.

E.g. it may show how long and where a mutex is waited for.

Signed-off-by: Andrew Vagin 
Signed-off-by: Peter Zijlstra 
Link: http://lkml.kernel.org/r/1322471015-107825-8-git-send-email-avagin@openvz.org
Signed-off-by: Ingo Molnar

sched, tracing: Show PREEMPT_ACTIVE state in trace_sched_switch

2011-09-26T11:25:54+00:00

We had need to see the difference between scheduling a runnable task and
a runnable task being involuntarily preempted.

No app should rely on the old string output (the binary
trace event record format is not changed).

Signed-off-by: Peter Zijlstra 
Cc: Thomas Gleixner 
Cc: Steven Rostedt 
Link: http://lkml.kernel.org/r/1316164603.10174.11.camel@twins
Signed-off-by: Ingo Molnar

tracing/sched: Add sched_pi_setprio tracepoint

2010-09-21T14:56:41+00:00

Add a tracepoint that shows the priority of a task being boosted
via priority inheritance.

Cc: Gregory Haskins 
Acked-by: Peter Zijlstra 
Signed-off-by: Steven Rostedt

tracing: Convert more sched events to DEFINE_EVENT

2010-06-28T21:12:50+00:00

Convert sched_wait_task to DEFINE_EVENT, and save ~1K:

   text    data     bss     dec     hex filename
 104595    9424    4992  119011   1d0e3 kernel/sched.o.orig
 103619    9344    4992  117955   1ccc3 kernel/sched.o

No change in functionality.

Signed-off-by: Li Zefan 
LKML-Reference: <4BFA3787.2040800@cn.fujitsu.com>
Signed-off-by: Steven Rostedt

sched, trace: Fix sched_switch() prev_state argument

2010-06-01T07:27:17+00:00

For CONFIG_PREEMPT=y kernels the sched_switch(.prev_state) argument isn't
useful because we can get preempted with current->state != TASK_RUNNING
without actually getting removed from the runqueue.

Cure this by treating all preempted tasks as runnable from the tracer's
point of view.

Signed-off-by: Peter Zijlstra 
Cautiously-acked-by: Steven Rostedt 
LKML-Reference: <1275322715.27810.23323.camel@twins>
Signed-off-by: Ingo Molnar