Merge branch 'tracing-core-for-linus' of...

	trace_buf_size=nn[KMG]

			[FTRACE] will set tracing buffer size.

	trace_event=[event-list]

			[FTRACE] Set and start specified trace events in order

			to facilitate early boot debugging.

			See also Documentation/trace/events.txt

	trix=		[HW,OSS] MediaTrix AudioTrix Pro

			Format:

			<io>,<irq>,<dma>,<dma2>,<sb_io>,<sb_irq>,<sb_dma>,<mpu_io>,<mpu_irq>

 X - there is a mixture of events enabled and disabled

 ? - this file does not affect any event

2.3 Boot option

---------------

In order to facilitate early boot debugging, use boot option:

	trace_event=[event-list]

The format of this boot option is the same as described in section 2.1.

3. Defining an event-enabled tracepoint

=======================================

	This file holds the output of the trace in a human

	readable format (described below).

  latency_trace:

	This file shows the same trace but the information

	is organized more to display possible latencies

	in the system (described below).

  trace_pipe:

	The output is the same as the "trace" file but this

	file is meant to be streamed with live tracing.

	Reads from this file will block until new data

	is retrieved. Unlike the "trace" and "latency_trace"

	files, this file is a consumer. This means reading

	from this file causes sequential reads to display

	more current data. Once data is read from this

	file, it is consumed, and will not be read

	again with a sequential read. The "trace" and

	"latency_trace" files are static, and if the

	tracer is not adding more data, they will display

	the same information every time they are read.

	Reads from this file will block until new data is

	retrieved.  Unlike the "trace" file, this file is a

	consumer. This means reading from this file causes

	sequential reads to display more current data. Once

	data is read from this file, it is consumed, and

	will not be read again with a sequential read. The

	"trace" file is static, and if the tracer is not

	adding more data,they will display the same

	information every time they are read.

  trace_options:

	Some of the tracers record the max latency.

	For example, the time interrupts are disabled.

	This time is saved in this file. The max trace

	will also be stored, and displayed by either

	"trace" or "latency_trace".  A new max trace will

	only be recorded if the latency is greater than

	the value in this file. (in microseconds)

	will also be stored, and displayed by "trace".

	A new max trace will only be recorded if the

	latency is greater than the value in this

	file. (in microseconds)

  buffer_size_kb:

	the trace with the longest max latency.

	See tracing_max_latency. When a new max is recorded,

	it replaces the old trace. It is best to view this

	trace via the latency_trace file.

	trace with the latency-format option enabled.

  "preemptoff"

Latency trace format

--------------------

For traces that display latency times, the latency_trace file

gives somewhat more information to see why a latency happened.

When the latency-format option is enabled, the trace file gives

somewhat more information to see why a latency happened.

Here is a typical trace.

# tracer: irqsoff

The above is mostly meaningful for kernel developers.

  time: This differs from the trace file output. The trace file output

	includes an absolute timestamp. The timestamp used by the

	latency_trace file is relative to the start of the trace.

  time: When the latency-format option is enabled, the trace file

	output includes a timestamp relative to the start of the

	trace. This differs from the output when latency-format

	is disabled, which includes an absolute timestamp.

  delay: This is just to help catch your eye a bit better. And

	 needs to be fixed to be only relative to the same CPU.

  sym-addr:

   bash-4000  [01]  1477.606694: simple_strtoul <c0339346>

  verbose - This deals with the latency_trace file.

  verbose - This deals with the trace file when the

            latency-format option is enabled.

    bash  4000 1 0 00000000 00010a95 [58127d26] 1720.415ms \

    (+0.000ms): simple_strtoul (strict_strtoul)

		the app is no longer running

		The lookup is performed when you read

		trace,trace_pipe,latency_trace. Example:

		trace,trace_pipe. Example:

		a.out-1623  [000] 40874.465068: /root/a.out[+0x480] <-/root/a.out[+0

x494] <- /root/a.out[+0x4a8] <- /lib/libc-2.7.so[+0x1e1a6]

	       every scheduling event. Will add overhead if

	       there's a lot of tasks running at once.

  latency-format - This option changes the trace. When

                   it is enabled, the trace displays

                   additional information about the

                   latencies, as described in "Latency

                   trace format".

sched_switch

------------

an example:

 # echo irqsoff > current_tracer

 # echo latency-format > trace_options

 # echo 0 > tracing_max_latency

 # echo 1 > tracing_enabled

 # ls -ltr

 [...]

 # echo 0 > tracing_enabled

 # cat latency_trace

 # cat trace

# tracer: irqsoff

#

irqsoff latency trace v1.1.5 on 2.6.26

is much like the irqsoff tracer.

 # echo preemptoff > current_tracer

 # echo latency-format > trace_options

 # echo 0 > tracing_max_latency

 # echo 1 > tracing_enabled

 # ls -ltr

 [...]

 # echo 0 > tracing_enabled

 # cat latency_trace

 # cat trace

# tracer: preemptoff

#

preemptoff latency trace v1.1.5 on 2.6.26-rc8

tracers.

 # echo preemptirqsoff > current_tracer

 # echo latency-format > trace_options

 # echo 0 > tracing_max_latency

 # echo 1 > tracing_enabled

 # ls -ltr

 [...]

 # echo 0 > tracing_enabled

 # cat latency_trace

 # cat trace

# tracer: preemptirqsoff

#

preemptirqsoff latency trace v1.1.5 on 2.6.26-rc8

'chrt' which changes the priority of the task.

 # echo wakeup > current_tracer

 # echo latency-format > trace_options

 # echo 0 > tracing_max_latency

 # echo 1 > tracing_enabled

 # chrt -f 5 sleep 1

 # echo 0 > tracing_enabled

 # cat latency_trace

 # cat trace

# tracer: wakeup

#

wakeup latency trace v1.1.5 on 2.6.26-rc8

" Enable folding for ftrace function_graph traces.

"

" To use, :source this file while viewing a function_graph trace, or use vim's

" -S option to load from the command-line together with a trace.  You can then

" use the usual vim fold commands, such as "za", to open and close nested

" functions.  While closed, a fold will show the total time taken for a call,

" as would normally appear on the line with the closing brace.  Folded

" functions will not include finish_task_switch(), so folding should remain

" relatively sane even through a context switch.

"

" Note that this will almost certainly only work well with a

" single-CPU trace (e.g. trace-cmd report --cpu 1).

function! FunctionGraphFoldExpr(lnum)

  let line = getline(a:lnum)

  if line[-1:] == '{'

    if line =~ 'finish_task_switch() {$'

      return '>1'

    endif

    return 'a1'

  elseif line[-1:] == '}'

    return 's1'

  else

    return '='

  endif

endfunction

function! FunctionGraphFoldText()

  let s = split(getline(v:foldstart), '|', 1)

  if getline(v:foldend+1) =~ 'finish_task_switch() {$'

    let s[2] = ' task switch  '

  else

    let e = split(getline(v:foldend), '|', 1)

    let s[2] = e[2]

  endif

  return join(s, '|')

endfunction

setlocal foldexpr=FunctionGraphFoldExpr(v:lnum)

setlocal foldtext=FunctionGraphFoldText()

setlocal foldcolumn=12

setlocal foldmethod=expr