1TRACE-CMD-EXTRACT(1)            [FIXME: manual]           TRACE-CMD-EXTRACT(1)
2
3
4

NAME

6       trace-cmd-extract - extract out the data from the Ftrace Linux tracer.
7

SYNOPSIS

9       trace-cmd extract [OPTIONS]
10

DESCRIPTION

12       The trace-cmd(1) extract is usually used after trace-cmd-start(1) and
13       trace-cmd-stop(1). It can be used after the Ftrace tracer has been
14       started manually through the Ftrace pseudo file system.
15
16       The extract command creates a trace.dat file that can be used by
17       trace-cmd-report(1) to read from. It reads the kernel internal ring
18       buffer to produce the trace.dat file.
19

OPTIONS

21       -p plugin
22           Although extract does not start any traces, some of the plugins
23           require just reading the output in ASCII format. These are the
24           latency tracers, since the latency tracers have a separate internal
25           buffer. The plugin option is therefore only necessary for the
26           wakeup, wakeup-rt, irqsoff, preemptoff and preemptirqsoff plugins.
27
28               With out this option, the extract command will extract from the internal
29               Ftrace buffers.
30
31       -O option
32           If a latency tracer is being extracted, and the -p option is used,
33           then there are some Ftrace options that can change the format. This
34           will update those options before extracting. To see the list of
35           options see trace-cmd-list. To enable an option, write its name, to
36           disable the option append the characters no to it. For example:
37           noprint-parent will disable the print-parent option that prints the
38           parent function in printing a function event.
39
40       -o outputfile
41           By default, the extract command will create a trace.dat file. This
42           option will change where the file is written to.
43
44       --date
45           This is the same as the trace-cmd-record(1) --date option, but it
46           does cause the extract routine to disable all tracing. That is, the
47           end of the extract will perform something similar to
48           trace-cmd-reset(1).
49

SEE ALSO

51       trace-cmd(1), trace-cmd-record(1), trace-cmd-report(1),
52       trace-cmd-start(1), trace-cmd-stop(1), trace-cmd-reset(1),
53       trace-cmd-split(1), trace-cmd-list(1), trace-cmd-listen(1)
54

AUTHOR

56       Written by Steven Rostedt, <rostedt@goodmis.org[1]>
57

RESOURCES

59       git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/trace-cmd.git
60

COPYING

62       Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted
63       under the terms of the GNU Public License (GPL).
64

NOTES

66        1. rostedt@goodmis.org
67           mailto:rostedt@goodmis.org
68
69
70
71[FIXME: source]                   03/23/2017              TRACE-CMD-EXTRACT(1)
Impressum