TrxShell [ mangaberri.com ]

Name	Size	Permission
trace-cmd-agent.1.html	19.89 KB	-rw-r--r--
trace-cmd-attach.1.html	25.27 KB	-rw-r--r--
trace-cmd-check-events.1.html	19.18 KB	-rw-r--r--
trace-cmd-clear.1.html	18.82 KB	-rw-r--r--
trace-cmd-convert.1.html	19.7 KB	-rw-r--r--
trace-cmd-dump.1.html	30.77 KB	-rw-r--r--
trace-cmd-extract.1.html	21.84 KB	-rw-r--r--
trace-cmd-hist.1.html	18.8 KB	-rw-r--r--
trace-cmd-list.1.html	20.89 KB	-rw-r--r--
trace-cmd-listen.1.html	19.93 KB	-rw-r--r--
trace-cmd-mem.1.html	20.93 KB	-rw-r--r--
trace-cmd-options.1.html	17.81 KB	-rw-r--r--
trace-cmd-profile.1.html	52.53 KB	-rw-r--r--
trace-cmd-record.1.html	67.98 KB	-rw-r--r--
trace-cmd-report.1.html	93.27 KB	-rw-r--r--
trace-cmd-reset.1.html	22.66 KB	-rw-r--r--
trace-cmd-restore.1.html	22.12 KB	-rw-r--r--
trace-cmd-set.1.html	33.07 KB	-rw-r--r--
trace-cmd-show.1.html	21.02 KB	-rw-r--r--
trace-cmd-snapshot.1.html	19.22 KB	-rw-r--r--
trace-cmd-split.1.html	21.96 KB	-rw-r--r--
trace-cmd-stack.1.html	18.75 KB	-rw-r--r--
trace-cmd-start.1.html	18.87 KB	-rw-r--r--
trace-cmd-stat.1.html	20.27 KB	-rw-r--r--
trace-cmd-stop.1.html	19.53 KB	-rw-r--r--
trace-cmd-stream.1.html	18.69 KB	-rw-r--r--
trace-cmd.1.html	22.71 KB	-rw-r--r--
trace-cmd.dat.v6.5.html	31.13 KB	-rw-r--r--
trace-cmd.dat.v7.5.html	43.07 KB	-rw-r--r--

Code Editor : trace-cmd-record.1.html

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
<head>
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
<meta name="generator" content="AsciiDoc 10.2.0" />
<title>TRACE-CMD-RECORD(1)</title>
<style type="text/css">
/* Shared CSS for AsciiDoc xhtml11 and html5 backends */

/* Default font. */
body {
  font-family: Georgia,serif;
}

/* Title font. */
h1, h2, h3, h4, h5, h6,
div.title, caption.title,
thead, p.table.header,
#toctitle,
#author, #revnumber, #revdate, #revremark,
#footer {
  font-family: Arial,Helvetica,sans-serif;
}

body {
  margin: 1em 5% 1em 5%;
}

a {
  color: blue;
  text-decoration: underline;
}
a:visited {
  color: fuchsia;
}

em {
  font-style: italic;
  color: navy;
}

strong {
  font-weight: bold;
  color: #083194;
}

h1, h2, h3, h4, h5, h6 {
  color: #527bbd;
  margin-top: 1.2em;
  margin-bottom: 0.5em;
  line-height: 1.3;
}

h1, h2, h3 {
  border-bottom: 2px solid silver;
}
h2 {
  padding-top: 0.5em;
}
h3 {
  float: left;
}
h3 + * {
  clear: left;
}
h5 {
  font-size: 1.0em;
}

div.sectionbody {
  margin-left: 0;
}

hr {
  border: 1px solid silver;
}

p {
  margin-top: 0.5em;
  margin-bottom: 0.5em;
}

ul, ol, li > p {
  margin-top: 0;
}
ul > li     { color: #aaa; }
ul > li > * { color: black; }

.monospaced, code, pre {
  font-family: "Courier New", Courier, monospace;
  font-size: inherit;
  color: navy;
  padding: 0;
  margin: 0;
}
pre {
  white-space: pre-wrap;
}

#author {
  color: #527bbd;
  font-weight: bold;
  font-size: 1.1em;
}
#email {
}
#revnumber, #revdate, #revremark {
}

#footer {
  font-size: small;
  border-top: 2px solid silver;
  padding-top: 0.5em;
  margin-top: 4.0em;
}
#footer-text {
  float: left;
  padding-bottom: 0.5em;
}
#footer-badges {
  float: right;
  padding-bottom: 0.5em;
}

#preamble {
  margin-top: 1.5em;
  margin-bottom: 1.5em;
}
div.imageblock, div.exampleblock, div.verseblock,
div.quoteblock, div.literalblock, div.listingblock, div.sidebarblock,
div.admonitionblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
div.admonitionblock {
  margin-top: 2.0em;
  margin-bottom: 2.0em;
  margin-right: 10%;
  color: #606060;
}

div.content { /* Block element content. */
  padding: 0;
}

/* Block element titles. */
div.title, caption.title {
  color: #527bbd;
  font-weight: bold;
  text-align: left;
  margin-top: 1.0em;
  margin-bottom: 0.5em;
}
div.title + * {
  margin-top: 0;
}

td div.title:first-child {
  margin-top: 0.0em;
}
div.content div.title:first-child {
  margin-top: 0.0em;
}
div.content + div.title {
  margin-top: 0.0em;
}

div.sidebarblock > div.content {
  background: #ffffee;
  border: 1px solid #dddddd;
  border-left: 4px solid #f0f0f0;
  padding: 0.5em;
}

div.listingblock > div.content {
  border: 1px solid #dddddd;
  border-left: 5px solid #f0f0f0;
  background: #f8f8f8;
  padding: 0.5em;
}

div.quoteblock, div.verseblock {
  padding-left: 1.0em;
  margin-left: 1.0em;
  margin-right: 10%;
  border-left: 5px solid #f0f0f0;
  color: #888;
}

div.quoteblock > div.attribution {
  padding-top: 0.5em;
  text-align: right;
}

div.verseblock > pre.content {
  font-family: inherit;
  font-size: inherit;
}
div.verseblock > div.attribution {
  padding-top: 0.75em;
  text-align: left;
}
/* DEPRECATED: Pre version 8.2.7 verse style literal block. */
div.verseblock + div.attribution {
  text-align: left;
}

div.admonitionblock .icon {
  vertical-align: top;
  font-size: 1.1em;
  font-weight: bold;
  text-decoration: underline;
  color: #527bbd;
  padding-right: 0.5em;
}
div.admonitionblock td.content {
  padding-left: 0.5em;
  border-left: 3px solid #dddddd;
}

div.exampleblock > div.content {
  border-left: 3px solid #dddddd;
  padding-left: 0.5em;
}

div.imageblock div.content { padding-left: 0; }
span.image img { border-style: none; vertical-align: text-bottom; }
a.image:visited { color: white; }

dl {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
}
dt {
  margin-top: 0.5em;
  margin-bottom: 0;
  font-style: normal;
  color: navy;
}
dd > *:first-child {
  margin-top: 0.1em;
}

ul, ol {
    list-style-position: outside;
}
ol.arabic {
  list-style-type: decimal;
}
ol.loweralpha {
  list-style-type: lower-alpha;
}
ol.upperalpha {
  list-style-type: upper-alpha;
}
ol.lowerroman {
  list-style-type: lower-roman;
}
ol.upperroman {
  list-style-type: upper-roman;
}

div.compact ul, div.compact ol,
div.compact p, div.compact p,
div.compact div, div.compact div {
  margin-top: 0.1em;
  margin-bottom: 0.1em;
}

tfoot {
  font-weight: bold;
}
td > div.verse {
  white-space: pre;
}

div.hdlist {
  margin-top: 0.8em;
  margin-bottom: 0.8em;
}
div.hdlist tr {
  padding-bottom: 15px;
}
dt.hdlist1.strong, td.hdlist1.strong {
  font-weight: bold;
}
td.hdlist1 {
  vertical-align: top;
  font-style: normal;
  padding-right: 0.8em;
  color: navy;
}
td.hdlist2 {
  vertical-align: top;
}
div.hdlist.compact tr {
  margin: 0;
  padding-bottom: 0;
}

.comment {
  background: yellow;
}

.footnote, .footnoteref {
  font-size: 0.8em;
}

span.footnote, span.footnoteref {
  vertical-align: super;
}

#footnotes {
  margin: 20px 0 20px 0;
  padding: 7px 0 0 0;
}

#footnotes div.footnote {
  margin: 0 0 5px 0;
}

#footnotes hr {
  border: none;
  border-top: 1px solid silver;
  height: 1px;
  text-align: left;
  margin-left: 0;
  width: 20%;
  min-width: 100px;
}

div.colist td {
  padding-right: 0.5em;
  padding-bottom: 0.3em;
  vertical-align: top;
}
div.colist td img {
  margin-top: 0.3em;
}

@media print {
  #footer-badges { display: none; }
}

#toc {
  margin-bottom: 2.5em;
}

#toctitle {
  color: #527bbd;
  font-size: 1.1em;
  font-weight: bold;
  margin-top: 1.0em;
  margin-bottom: 0.1em;
}

div.toclevel0, div.toclevel1, div.toclevel2, div.toclevel3, div.toclevel4 {
  margin-top: 0;
  margin-bottom: 0;
}
div.toclevel2 {
  margin-left: 2em;
  font-size: 0.9em;
}
div.toclevel3 {
  margin-left: 4em;
  font-size: 0.9em;
}
div.toclevel4 {
  margin-left: 6em;
  font-size: 0.9em;
}

span.aqua { color: aqua; }
span.black { color: black; }
span.blue { color: blue; }
span.fuchsia { color: fuchsia; }
span.gray { color: gray; }
span.green { color: green; }
span.lime { color: lime; }
span.maroon { color: maroon; }
span.navy { color: navy; }
span.olive { color: olive; }
span.purple { color: purple; }
span.red { color: red; }
span.silver { color: silver; }
span.teal { color: teal; }
span.white { color: white; }
span.yellow { color: yellow; }

span.aqua-background { background: aqua; }
span.black-background { background: black; }
span.blue-background { background: blue; }
span.fuchsia-background { background: fuchsia; }
span.gray-background { background: gray; }
span.green-background { background: green; }
span.lime-background { background: lime; }
span.maroon-background { background: maroon; }
span.navy-background { background: navy; }
span.olive-background { background: olive; }
span.purple-background { background: purple; }
span.red-background { background: red; }
span.silver-background { background: silver; }
span.teal-background { background: teal; }
span.white-background { background: white; }
span.yellow-background { background: yellow; }

span.big { font-size: 2em; }
span.small { font-size: 0.6em; }

span.underline { text-decoration: underline; }
span.overline { text-decoration: overline; }
span.line-through { text-decoration: line-through; }

div.unbreakable { page-break-inside: avoid; }

/*
 * xhtml11 specific
 *
 * */

div.tableblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
div.tableblock > table {
  border: 3px solid #527bbd;
}
thead, p.table.header {
  font-weight: bold;
  color: #527bbd;
}
p.table {
  margin-top: 0;
}
/* Because the table frame attribute is overridden by CSS in most browsers. */
div.tableblock > table[frame="void"] {
  border-style: none;
}
div.tableblock > table[frame="hsides"] {
  border-left-style: none;
  border-right-style: none;
}
div.tableblock > table[frame="vsides"] {
  border-top-style: none;
  border-bottom-style: none;
}

/*
 * html5 specific
 *
 * */

table.tableblock {
  margin-top: 1.0em;
  margin-bottom: 1.5em;
}
thead, p.tableblock.header {
  font-weight: bold;
  color: #527bbd;
}
p.tableblock {
  margin-top: 0;
}
table.tableblock {
  border-width: 3px;
  border-spacing: 0px;
  border-style: solid;
  border-color: #527bbd;
  border-collapse: collapse;
}
th.tableblock, td.tableblock {
  border-width: 1px;
  padding: 4px;
  border-style: solid;
  border-color: #527bbd;
}

table.tableblock.frame-topbot {
  border-left-style: hidden;
  border-right-style: hidden;
}
table.tableblock.frame-sides {
  border-top-style: hidden;
  border-bottom-style: hidden;
}
table.tableblock.frame-none {
  border-style: hidden;
}

th.tableblock.halign-left, td.tableblock.halign-left {
  text-align: left;
}
th.tableblock.halign-center, td.tableblock.halign-center {
  text-align: center;
}
th.tableblock.halign-right, td.tableblock.halign-right {
  text-align: right;
}

th.tableblock.valign-top, td.tableblock.valign-top {
  vertical-align: top;
}
th.tableblock.valign-middle, td.tableblock.valign-middle {
  vertical-align: middle;
}
th.tableblock.valign-bottom, td.tableblock.valign-bottom {
  vertical-align: bottom;
}

/*
 * manpage specific
 *
 * */

body.manpage h1 {
  padding-top: 0.5em;
  padding-bottom: 0.5em;
  border-top: 2px solid silver;
  border-bottom: 2px solid silver;
}
body.manpage h2 {
  border-style: none;
}
body.manpage div.sectionbody {
  margin-left: 3em;
}

@media print {
  body.manpage div#toc { display: none; }
}

</style>
<script type="text/javascript">
/*<![CDATA[*/
var asciidoc = { // Namespace.

/////////////////////////////////////////////////////////////////////
// Table Of Contents generator
/////////////////////////////////////////////////////////////////////

/* Author: Mihai Bazon, September 2002
 * http://students.infoiasi.ro/~mishoo
 *
 * Table Of Content generator
 * Version: 0.4
 *
 * Feel free to use this script under the terms of the GNU General Public
 * License, as long as you do not remove or alter this notice.
 */

/* modified by Troy D. Hanson, September 2006. License: GPL */
 /* modified by Stuart Rackham, 2006, 2009. License: GPL */

// toclevels = 1..4.
toc: function (toclevels) {

function getText(el) {
    var text = "";
    for (var i = el.firstChild; i != null; i = i.nextSibling) {
      if (i.nodeType == 3 /* Node.TEXT_NODE */) // IE doesn't speak constants.
        text += i.data;
      else if (i.firstChild != null)
        text += getText(i);
    }
    return text;
  }

function TocEntry(el, text, toclevel) {
    this.element = el;
    this.text = text;
    this.toclevel = toclevel;
  }

var toc = document.getElementById("toc");
  if (!toc) {
    return;
  }

// Delete existing TOC entries in case we're reloading the TOC.
 var tocEntriesToRemove = [];
 var i;
 for (i = 0; i < toc.childNodes.length; i++) {
 var entry = toc.childNodes[i];
 if (entry.nodeName.toLowerCase() == 'div'
 && entry.getAttribute("class")
 && entry.getAttribute("class").match(/^toclevel/))
 tocEntriesToRemove.push(entry);
 }
 for (i = 0; i < tocEntriesToRemove.length; i++) {
 toc.removeChild(tocEntriesToRemove[i]);
 }

// Rebuild TOC entries.
 var entries = tocEntries(document.getElementById("content"), toclevels);
 for (var i = 0; i < entries.length; ++i) {
 var entry = entries[i];
 if (entry.element.id == "")
 entry.element.id = "_toc_" + i;
 var a = document.createElement("a");
 a.href = "#" + entry.element.id;
 a.appendChild(document.createTextNode(entry.text));
 var div = document.createElement("div");
 div.appendChild(a);
 div.className = "toclevel" + entry.toclevel;
 toc.appendChild(div);
 }
 if (entries.length == 0)
 toc.parentNode.removeChild(toc);
},

/////////////////////////////////////////////////////////////////////
// Footnotes generator
/////////////////////////////////////////////////////////////////////

/* Based on footnote generation code from:
 * http://www.brandspankingnew.net/archive/2005/07/format_footnote.html
 */

footnotes: function () {
 // Delete existing footnote entries in case we're reloading the footnodes.
 var i;
 var noteholder = document.getElementById("footnotes");
 if (!noteholder) {
 return;
 }
 var entriesToRemove = [];
 for (i = 0; i < noteholder.childNodes.length; i++) {
 var entry = noteholder.childNodes[i];
 if (entry.nodeName.toLowerCase() == 'div' && entry.getAttribute("class") == "footnote")
 entriesToRemove.push(entry);
 }
 for (i = 0; i < entriesToRemove.length; i++) {
 noteholder.removeChild(entriesToRemove[i]);
 }

// Rebuild footnote entries.
 var cont = document.getElementById("content");
 var spans = cont.getElementsByTagName("span");
 var refs = {};
 var n = 0;
 for (i=0; i<spans.length; i++) {
 if (spans[i].className == "footnote") {
 n++;
 var note = spans[i].getAttribute("data-note");
 if (!note) {
 // Use [\s\S] in place of . so multi-line matches work.
 // Because JavaScript has no s (dotall) regex flag.
 note = spans[i].innerHTML.match(/\s*\[([\s\S]*)]\s*/)[1];
 spans[i].innerHTML =
 "[<a id='_footnoteref_" + n + "' href='#_footnote_" + n +
 "' title='View footnote' class='footnote'>" + n + "</a>]";
 spans[i].setAttribute("data-note", note);
 }
 noteholder.innerHTML +=
 "<div class='footnote' id='_footnote_" + n + "'>" +
 "<a href='#_footnoteref_" + n + "' title='Return to text'>" +
 n + "</a>. " + note + "</div>";
 var id =spans[i].getAttribute("id");
 if (id != null) refs["#"+id] = n;
 }
 }
 if (n == 0)
 noteholder.parentNode.removeChild(noteholder);
 else {
 // Process footnoterefs.
 for (i=0; i<spans.length; i++) {
 if (spans[i].className == "footnoteref") {
 var href = spans[i].getElementsByTagName("a")[0].getAttribute("href");
 href = href.match(/#.*/)[0]; // Because IE return full URL.
 n = refs[href];
 spans[i].innerHTML =
 "[<a href='#_footnote_" + n +
 "' title='View footnote' class='footnote'>" + n + "</a>]";
 }
 }
 }
},

install: function(toclevels) {
  var timerId;

function reinstall() {
    asciidoc.footnotes();
    if (toclevels) {
      asciidoc.toc(toclevels);
    }
  }

function reinstallAndRemoveTimer() {
    clearInterval(timerId);
    reinstall();
  }

timerId = setInterval(reinstall, 500);
  if (document.addEventListener)
    document.addEventListener("DOMContentLoaded", reinstallAndRemoveTimer, false);
  else
    window.onload = reinstallAndRemoveTimer;
}

}
asciidoc.install();
/*]]>*/
</script>
</head>
<body class="manpage">
<div id="header">
<h1>
TRACE-CMD-RECORD(1) Manual Page
</h1>
<h2>NAME</h2>
<div class="sectionbody">
trace-cmd-record -
 record a trace from the Ftrace Linux internal tracer

</div>
</div>
<div id="content">
<div class="sect1">
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="paragraph">trace-cmd record [OPTIONS] [command]</div>
</div>
</div>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph">The trace-cmd(1) record command will set up the Ftrace Linux kernel tracer to
record the specified plugins or events that happen while the command
executes. If no command is given, then it will record until the user hits
Ctrl-C.</div>
<div class="paragraph">The record command of trace-cmd will set up the Ftrace tracer to start tracing
the various events or plugins that are given on the command line. It will then
create a number of tracing processes (one per CPU) that will start recording
from the kernel ring buffer straight into temporary files. When the command is
complete (or Ctrl-C is hit) all the files will be combined into a trace.dat
file that can later be read (see trace-cmd-report(1)).</div>
</div>
</div>
<div class="sect1">
<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
-p tracer
</dt>
<dd>

 Specify a tracer. Tracers usually do more than just trace an event.
 Common tracers are: function, function_graph, preemptirqsoff,
 irqsoff, preemptoff and wakeup. A tracer must be supported by the
 running kernel. To see a list of available tracers, see trace-cmd-list(1).

</dd>
<dt class="hdlist1">
-e event
</dt>
<dd>

 Specify an event to trace. Various static trace points have been added to
 the Linux kernel. They are grouped by subsystem where you can enable all
 events of a given subsystem or specify specific events to be enabled. The
 event is of the format "subsystem:event-name". You can also just specify
 the subsystem without the :event-name or the event-name without the
 "subsystem:". Using "-e sched_switch" will enable the "sched_switch" event
 where as, "-e sched" will enable all events under the "sched" subsystem.

<div class="literalblock">
<div class="content">
<pre><code>The 'event' can also contain glob expressions. That is, "*stat*" will
select all events (or subsystems) that have the characters "stat" in their
names.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The keyword 'all' can be used to enable all events.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-a
</dt>
<dd>

 Every event that is being recorded has its output format file saved
 in the output file to be able to display it later. But if other
 events are enabled in the trace without trace-cmd&#8217;s knowledge, the
 formats of those events will not be recorded and trace-cmd report will
 not be able to display them. If this is the case, then specify the
 -a option and the format for all events in the system will be saved.

</dd>
<dt class="hdlist1">
-T
</dt>
<dd>

 Enable a stacktrace on each event. For example:

<div class="literalblock">
<div class="content">
<pre><code> &lt;idle&gt;-0 [003] 58549.289091: sched_switch: kworker/0:1:0 [120] R ==&gt; trace-cmd:2603 [120]
 &lt;idle&gt;-0 [003] 58549.289092: kernel_stack: &lt;stack trace&gt;
=&gt; schedule (ffffffff814b260e)
=&gt; cpu_idle (ffffffff8100a38c)
=&gt; start_secondary (ffffffff814ab828)</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--func-stack
</dt>
<dd>

 Enable a stack trace on all functions. Note this is only applicable
 for the "function" plugin tracer, and will only take effect if the
 -l option is used and succeeds in limiting functions. If the function
 tracer is not filtered, and the stack trace is enabled, you can live
 lock the machine.

</dd>
<dt class="hdlist1">
-f filter
</dt>
<dd>

 Specify a filter for the previous event. This must come after a -e. This
 will filter what events get recorded based on the content of the event.
 Filtering is passed to the kernel directly so what filtering is allowed
 may depend on what version of the kernel you have. Basically, it will
 let you use C notation to check if an event should be processed or not.

</dd>
</dl></div>
<div class="listingblock">
<div class="content">
<pre><tt> ==, &gt;=, &lt;=, &gt;, &lt;, &amp;, |, &amp;&amp; and ||</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>The above are usually safe to use to compare fields.</code></pre>
</div></div>
<div class="dlist"><dl>
<dt class="hdlist1">
--no-filter
</dt>
<dd>

 Do not filter out the trace-cmd threads. By default, the threads are
 filtered out to not be traced by events. This option will have the trace-cmd
 threads also be traced.

</dd>
<dt class="hdlist1">
-R trigger
</dt>
<dd>

 Specify a trigger for the previous event. This must come after a -e.
 This will add a given trigger to the given event. To only enable the trigger
 and not the event itself, then place the event after the -v option.

<div class="literalblock">
<div class="content">
<pre><code>See Documentation/trace/events.txt in the Linux kernel source for more
information on triggers.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-v
</dt>
<dd>

 This will cause all events specified after it on the command line to not
 be traced. This is useful for selecting a subsystem to be traced but to
 leave out various events. For Example: "-e sched -v -e "*stat\*"" will
 enable all events in the sched subsystem except those that have "stat" in
 their names.

<div class="literalblock">
<div class="content">
<pre><code>Note: the *-v* option was taken from the way grep(1) inverts the following
matches.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-F
</dt>
<dd>

 This will filter only the executable that is given on the command line. If
 no command is given, then it will filter itself (pretty pointless).
 Using -F will let you trace only events that are caused by the given
 command.

</dd>
<dt class="hdlist1">
-P pid
</dt>
<dd>

 Similar to -F but lets you specify a process ID to trace.

</dd>
<dt class="hdlist1">
-c
</dt>
<dd>

 Used with either -F (or -P if kernel supports it) to trace the process'
 children too.

</dd>
<dt class="hdlist1">
--user
</dt>
<dd>

 Execute the specified command as given user.

</dd>
<dt class="hdlist1">
-C clock
</dt>
<dd>

 Set the trace clock to "clock".

<div class="literalblock">
<div class="content">
<pre><code>Use trace-cmd(1) list -C to see what clocks are available.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-o output-file
</dt>
<dd>

 By default, trace-cmd report will create a trace.dat file. You can
 specify a different file to write to with the -o option.

</dd>
<dt class="hdlist1">
-l function-name
</dt>
<dd>

 This will limit the function and function_graph tracers to only trace
 the given function name. More than one -l may be specified on the
 command line to trace more than one function. This supports both full
 regex(3) parsing, or basic glob parsing. If the filter has only alphanumeric,
 _, *, ? and . characters, then it will be parsed as a basic glob.
 to force it to be a regex, prefix the filter with ^ or append it with $
 and it will then be parsed as a regex.

</dd>
<dt class="hdlist1">
-g function-name
</dt>
<dd>

 This option is for the function_graph plugin. It will graph the given
 function. That is, it will only trace the function and all functions that
 it calls. You can have more than one -g on the command line.

</dd>
<dt class="hdlist1">
-n function-name
</dt>
<dd>

 This has the opposite effect of -l. The function given with the -n
 option will not be traced. This takes precedence, that is, if you include
 the same function for both -n and -l, it will not be traced.

</dd>
<dt class="hdlist1">
-d
</dt>
<dd>

 Some tracer plugins enable the function tracer by default. Like the
 latency tracers. This option prevents the function tracer from being
 enabled at start up.

</dd>
<dt class="hdlist1">
-D
</dt>
<dd>

 The option -d will try to use the function-trace option to disable the
 function tracer (if available), otherwise it defaults to the proc file:
 /proc/sys/kernel/ftrace_enabled, but will not touch it if the function-trace
 option is available. The -D option will disable both the ftrace_enabled
 proc file as well as the function-trace option if it exists.

<div class="literalblock">
<div class="content">
<pre><code>Note, this disable function tracing for all users, which includes users
outside of ftrace tracers (stack_tracer, perf, etc).</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-O option
</dt>
<dd>

 Ftrace has various options that can be enabled or disabled. This allows
 you to set them. Appending the text no to an option disables it.
 For example: "-O nograph-time" will disable the "graph-time" Ftrace
 option.

</dd>
<dt class="hdlist1">
-s interval
</dt>
<dd>

 The processes that trace-cmd creates to record from the ring buffer need
 to wake up to do the recording. Setting the interval to zero will cause
 the processes to wakeup every time new data is written into the buffer.
 But since Ftrace is recording kernel activity, the act of this processes
 going back to sleep may cause new events into the ring buffer which will
 wake the process back up. This will needlessly add extra data into the
 ring buffer.

<div class="literalblock">
<div class="content">
<pre><code>The 'interval' metric is microseconds. The default is set to 1000 (1 ms).
This is the time each recording process will sleep before waking up to
record any new data that was written to the ring buffer.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-r priority
</dt>
<dd>

 The priority to run the capture threads at. In a busy system the trace
 capturing threads may be staved and events can be lost. This increases
 the priority of those threads to the real time (FIFO) priority.
 But use this option with care, it can also change the behaviour of
 the system being traced.

</dd>
<dt class="hdlist1">
-b size
</dt>
<dd>

 This sets the ring buffer size to size kilobytes. Because the Ftrace
 ring buffer is per CPU, this size is the size of each per CPU ring buffer
 inside the kernel. Using "-b 10000" on a machine with 4 CPUs will make
 Ftrace have a total buffer size of 40 Megs.

</dd>
<dt class="hdlist1">
-B buffer-name
</dt>
<dd>

 If the kernel supports multiple buffers, this will add a buffer with
 the given name. If the buffer name already exists, that buffer is just
 reset and will not be deleted at the end of record execution. If the
 buffer is created, it will be removed at the end of execution (unless
 the -k is set, or start command was used).

<div class="literalblock">
<div class="content">
<pre><code>After a buffer name is stated, all events added after that will be
associated with that buffer. If no buffer is specified, or an event
is specified before a buffer name, it will be associated with the
main (toplevel) buffer.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>trace-cmd record -e sched -B block -e block -B time -e timer sleep 1</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The above is will enable all sched events in the main buffer. It will
then create a 'block' buffer instance and enable all block events within
that buffer. A 'time' buffer instance is created and all timer events
will be enabled for that event.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-m size
</dt>
<dd>

 The max size in kilobytes that a per cpu buffer should be. Note, due
 to rounding to page size, the number may not be totally correct.
 Also, this is performed by switching between two buffers that are half
 the given size thus the output may not be of the given size even if
 much more was written.

<div class="literalblock">
<div class="content">
<pre><code>Use this to prevent running out of diskspace for long runs.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-M cpumask
</dt>
<dd>

 Set the cpumask for to trace. It only affects the last buffer instance
 given. If supplied before any buffer instance, then it affects the
 main buffer. The value supplied must be a hex number.

<div class="literalblock">
<div class="content">
<pre><code>trace-cmd record -p function -M c -B events13 -e all -M 5</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>If the -M is left out, then the mask stays the same. To enable all
CPUs, pass in a value of '-1'.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-k
</dt>
<dd>

 By default, when trace-cmd is finished tracing, it will reset the buffers
 and disable all the tracing that it enabled. This option keeps trace-cmd
 from disabling the tracer and reseting the buffer. This option is useful for
 debugging trace-cmd.

<div class="literalblock">
<div class="content">
<pre><code>Note: usually trace-cmd will set the "tracing_on" file back to what it
was before it was called. This option will leave that file set to zero.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-i
</dt>
<dd>

 By default, if an event is listed that trace-cmd does not find, it
 will exit with an error. This option will just ignore events that are
 listed on the command line but are not found on the system.

</dd>
<dt class="hdlist1">
-N host:port
</dt>
<dd>

 If another machine is running "trace-cmd listen", this option is used to
 have the data sent to that machine with UDP packets. Instead of writing
 to an output file, the data is sent off to a remote box. This is ideal for
 embedded machines with little storage, or having a single machine that
 will keep all the data in a single repository.

<div class="literalblock">
<div class="content">
<pre><code>Note: This option is not supported with latency tracer plugins:
 wakeup, wakeup_rt, irqsoff, preemptoff and preemptirqsoff</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-V cid:port
</dt>
<dd>

 If recording on a guest VM and the host is running trace-cmd listen with
 the -V option as well, or if this is recording on the host, and a guest
 in running trace-cmd listen with the -V option, then connect to the
 listener (the same as connecting with the -N option via the network).
 This has the same limitations as the -N option above with respect to
 latency tracer plugins.

</dd>
<dt class="hdlist1">
-t
</dt>
<dd>

 This option is used with -N, when there&#8217;s a need to send the live data
 with TCP packets instead of UDP. Although TCP is not nearly as fast as
 sending the UDP packets, but it may be needed if the network is not that
 reliable, the amount of data is not that intensive, and a guarantee is
 needed that all traced information is transfered successfully.

</dd>
<dt class="hdlist1">
-q | --quiet
</dt>
<dd>

 For use with recording an application. Suppresses normal output
 (except for errors) to allow only the application&#8217;s output to be displayed.

</dd>
<dt class="hdlist1">
--date
</dt>
<dd>

 With the --date option, "trace-cmd" will write timestamps into the
 trace buffer after it has finished recording. It will then map the
 timestamp to gettimeofday which will allow wall time output from the
 timestamps reading the created trace.dat file.

</dd>
<dt class="hdlist1">
--max-graph-depth depth
</dt>
<dd>

 Set the maximum depth the function_graph tracer will trace into a function.
 A value of one will only show where userspace enters the kernel but not any
 functions called in the kernel. The default is zero, which means no limit.

</dd>
<dt class="hdlist1">
--cmdlines-size size
</dt>
<dd>

 Set the number of entries the kernel tracing file "saved_cmdlines" can
 contain. This file is a circular buffer which stores the mapping between
 cmdlines and PIDs. If full, it leads to unresolved cmdlines ("&lt;&#8230;&gt;") within
 the trace. The kernel default value is 128.

</dd>
<dt class="hdlist1">
--module module
</dt>
<dd>

 Filter a module&#8217;s name in function tracing. It is equivalent to adding
 :mod:module after all other functions being filtered. If no other function
 filter is listed, then all modules functions will be filtered in the filter.

<div class="literalblock">
<div class="content">
<pre><code>'--module snd' is equivalent to '-l :mod:snd'</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'--module snd -l "*jack*"' is equivalent to '-l "*jack*:mod:snd"'</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'--module snd -n "*"' is equivalent to '-n :mod:snd'</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--proc-map
</dt>
<dd>

 Save the traced process address map into the trace.dat file. The traced
 processes can be specified using the option -P, or as a given command.

</dd>
<dt class="hdlist1">
--profile
</dt>
<dd>

 With the --profile option, "trace-cmd" will enable tracing that can
 be used with trace-cmd-report(1) --profile option. If a tracer -p is
 not set, and function graph depth is supported by the kernel, then
 the function_graph tracer will be enabled with a depth of one (only
 show where userspace enters into the kernel). It will also enable
 various tracepoints with stack tracing such that the report can show
 where tasks have been blocked for the longest time.

<div class="literalblock">
<div class="content">
<pre><code>See trace-cmd-profile(1) for more details and examples.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-G
</dt>
<dd>

 Set interrupt (soft and hard) events as global (associated to CPU
 instead of tasks). Only works for --profile.

</dd>
<dt class="hdlist1">
-H event-hooks
</dt>
<dd>

 Add custom event matching to connect any two events together. When not
 used with --profile, it will save the parameter and this will be
 used by trace-cmd report --profile, too. That is:

<div class="literalblock">
<div class="content">
<pre><code>trace-cmd record -H hrtimer_expire_entry,hrtimer/hrtimer_expire_exit,hrtimer,sp
trace-cmd report --profile</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Will profile hrtimer_expire_entry and hrtimer_expire_ext times.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>See trace-cmd-profile(1) for format.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-S
</dt>
<dd>

(for --profile only)
 Only enable the tracer or events speficied on the command line.
 With this option, the function_graph tracer is not enabled, nor are
 any events (like sched_switch), unless they are specifically specified
 on the command line (i.e. -p function -e sched_switch -e sched_wakeup)

</dd>
<dt class="hdlist1">
--temp directory
</dt>
<dd>

 When trace-cmd is recording the trace, it records the per CPU data into
 a separate file for each CPU. At the end of the trace, these files are
 concatenated onto the final trace.dat file. If the final file is on a network
 file system, it may not be appropriate to copy these temp files into the
 same location. --temp can be used to tell trace-cmd where those temp
 files should be created.

</dd>
<dt class="hdlist1">
--ts-offset offset
</dt>
<dd>

 Add an offset for the timestamp in the trace.dat file. This will add a
 offset option into the trace.dat file such that a trace-cmd report will
 offset all the timestamps of the events by the given offset. The offset
 is in raw units. That is, if the event timestamps are in nanoseconds
 the offset will also be in nanoseconds even if the displayed units are
 in microseconds.

</dd>
<dt class="hdlist1">
--tsync-interval
</dt>
<dd>

 Set the loop interval, in ms, for timestamps synchronization with guests:
 If a negative number is specified, timestamps synchronization is disabled
 If 0 is specified, no loop is performed - timestamps offset is calculated only twice,"
 at the beginning and at the end of the trace.
 Timestamps synchronization with guests works only if there is support for VSOCK.\n"

</dd>
<dt class="hdlist1">
--tsc2nsec
</dt>
<dd>

 Convert the current clock to nanoseconds, using tsc multiplier and shift from the Linux
 kernel&#8217;s perf interface. This option does not change the trace clock, just assumes that
 the tsc multiplier and shift are applicable for the selected clock. You may use the
 "-C tsc2nsec" clock, if not sure what clock to select.

</dd>
<dt class="hdlist1">
--stderr
</dt>
<dd>

 Have output go to stderr instead of stdout, but the output of the command
 executed will not be changed. This is useful if you want to monitor the
 output of the command being executed, but not see the output from trace-cmd.

</dd>
<dt class="hdlist1">
--poll
</dt>
<dd>

 Waiting for data to be available on the trace ring-buffers may trigger
 IPIs. This might generate unacceptable trace noise when tracing low latency
 or real time systems. The poll option forces trace-cmd to use O_NONBLOCK.
 Traces are extracted by busy waiting, which will hog the CPUs, so only use
 when really needed.

</dd>
<dt class="hdlist1">
--name
</dt>
<dd>

 Give a specific name for the current agent being processed. Used after -A to
 give the guest being traced a name. Useful when using the vsocket ID instead of
 a name of the guest.

</dd>
<dt class="hdlist1">
--verbose[=level]
</dt>
<dd>

 Set the log level. Supported log levels are "none", "critical", "error", "warning",
 "info", "debug", "all" or their identifiers "0", "1", "2", "3", "4", "5", "6". Setting the log
 level to specific value enables all logs from that and all previous levels.
 The level will default to "info" if one is not specified.

<div class="literalblock">
<div class="content">
<pre><code>Example: enable all critical, error and warning logs</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>trace-cmd record --verbose=warning</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--file-version
</dt>
<dd>

 Desired version of the output file. Supported versions are 6 or 7.

</dd>
<dt class="hdlist1">
--compression
</dt>
<dd>

 Compression of the trace output file, one of these strings can be passed:

<div class="literalblock">
<div class="content">
<pre><code>'any' - auto select the best available compression algorithm</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'none' - do not compress the trace file</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'name' - the name of the desired compression algorithms. Available algorithms can be listed with
trace-cmd list -c</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--proxy vsocket
</dt>
<dd>

 Use a vsocket proxy to reach the agent. Acts the same as -A (for an
 agent) but will send the proxy connection to the agent. It is expected to
 run on a privileged guest that the host is aware of (as denoted by the
 cid in the -P option for the agent).

</dd>
</dl></div>
</div>
</div>
<div class="sect1">
<h2 id="_examples">EXAMPLES</h2>
<div class="sectionbody">
<div class="paragraph">The basic way to trace all events:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd record -e all ls &gt; /dev/null
 # trace-cmd report
 trace-cmd-13541 [003] 106260.693809: filemap_fault: address=0x128122 offset=0xce
 trace-cmd-13543 [001] 106260.693809: kmalloc: call_site=81128dd4 ptr=0xffff88003dd83800 bytes_req=768 bytes_alloc=1024 gfp_flags=GFP_KERNEL|GFP_ZERO
 ls-13545 [002] 106260.693809: kfree: call_site=810a7abb ptr=0x0
 ls-13545 [002] 106260.693818: sys_exit_write: 0x1</tt></pre></div></div>
<div class="paragraph">To use the function tracer with sched switch tracing:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd record -p function -e sched_switch ls &gt; /dev/null
 # trace-cmd report
 ls-13587 [002] 106467.860310: function: hrtick_start_fair &lt;-- pick_next_task_fair
 ls-13587 [002] 106467.860313: sched_switch: prev_comm=trace-cmd prev_pid=13587 prev_prio=120 prev_state=R ==&gt; next_comm=trace-cmd next_pid=13583 next_prio=120
 trace-cmd-13585 [001] 106467.860314: function: native_set_pte_at &lt;-- __do_fault
 trace-cmd-13586 [003] 106467.860314: function: up_read &lt;-- do_page_fault
 ls-13587 [002] 106467.860317: function: __phys_addr &lt;-- schedule
 trace-cmd-13585 [001] 106467.860318: function: _raw_spin_unlock &lt;-- __do_fault
 ls-13587 [002] 106467.860320: function: native_load_sp0 &lt;-- __switch_to
 trace-cmd-13586 [003] 106467.860322: function: down_read_trylock &lt;-- do_page_fault</tt></pre></div></div>
<div class="paragraph">Here is a nice way to find what interrupts have the highest latency:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd record -p function_graph -e irq_handler_entry -l do_IRQ sleep 10
 # trace-cmd report
 &lt;idle&gt;-0 [000] 157412.933969: funcgraph_entry: | do_IRQ() {
 &lt;idle&gt;-0 [000] 157412.933974: irq_handler_entry: irq=48 name=eth0
 &lt;idle&gt;-0 [000] 157412.934004: funcgraph_exit: + 36.358 us | }
 &lt;idle&gt;-0 [000] 157413.895004: funcgraph_entry: | do_IRQ() {
 &lt;idle&gt;-0 [000] 157413.895011: irq_handler_entry: irq=48 name=eth0
 &lt;idle&gt;-0 [000] 157413.895026: funcgraph_exit: + 24.014 us | }
 &lt;idle&gt;-0 [000] 157415.891762: funcgraph_entry: | do_IRQ() {
 &lt;idle&gt;-0 [000] 157415.891769: irq_handler_entry: irq=48 name=eth0
 &lt;idle&gt;-0 [000] 157415.891784: funcgraph_exit: + 22.928 us | }
 &lt;idle&gt;-0 [000] 157415.934869: funcgraph_entry: | do_IRQ() {
 &lt;idle&gt;-0 [000] 157415.934874: irq_handler_entry: irq=48 name=eth0
 &lt;idle&gt;-0 [000] 157415.934906: funcgraph_exit: + 37.512 us | }
 &lt;idle&gt;-0 [000] 157417.888373: funcgraph_entry: | do_IRQ() {
 &lt;idle&gt;-0 [000] 157417.888381: irq_handler_entry: irq=48 name=eth0
 &lt;idle&gt;-0 [000] 157417.888398: funcgraph_exit: + 25.943 us | }</tt></pre></div></div>
<div class="paragraph">An example of the profile:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd record --profile sleep 1
 # trace-cmd report --profile --comm sleep
task: sleep-21611
 Event: sched_switch:R (1) Total: 99442 Avg: 99442 Max: 99442 Min:99442
 &lt;stack&gt; 1 total:99442 min:99442 max:99442 avg=99442
 =&gt; ftrace_raw_event_sched_switch (0xffffffff8105f812)
 =&gt; __schedule (0xffffffff8150810a)
 =&gt; preempt_schedule (0xffffffff8150842e)
 =&gt; ___preempt_schedule (0xffffffff81273354)
 =&gt; cpu_stop_queue_work (0xffffffff810b03c5)
 =&gt; stop_one_cpu (0xffffffff810b063b)
 =&gt; sched_exec (0xffffffff8106136d)
 =&gt; do_execve_common.isra.27 (0xffffffff81148c89)
 =&gt; do_execve (0xffffffff811490b0)
 =&gt; SyS_execve (0xffffffff811492c4)
 =&gt; return_to_handler (0xffffffff8150e3c8)
 =&gt; stub_execve (0xffffffff8150c699)
 Event: sched_switch:S (1) Total: 1000506680 Avg: 1000506680 Max: 1000506680 Min:1000506680
 &lt;stack&gt; 1 total:1000506680 min:1000506680 max:1000506680 avg=1000506680
 =&gt; ftrace_raw_event_sched_switch (0xffffffff8105f812)
 =&gt; __schedule (0xffffffff8150810a)
 =&gt; schedule (0xffffffff815084b8)
 =&gt; do_nanosleep (0xffffffff8150b22c)
 =&gt; hrtimer_nanosleep (0xffffffff8108d647)
 =&gt; SyS_nanosleep (0xffffffff8108d72c)
 =&gt; return_to_handler (0xffffffff8150e3c8)
 =&gt; tracesys_phase2 (0xffffffff8150c304)
 Event: sched_wakeup:21611 (1) Total: 30326 Avg: 30326 Max: 30326 Min:30326
 &lt;stack&gt; 1 total:30326 min:30326 max:30326 avg=30326
 =&gt; ftrace_raw_event_sched_wakeup_template (0xffffffff8105f653)
 =&gt; ttwu_do_wakeup (0xffffffff810606eb)
 =&gt; ttwu_do_activate.constprop.124 (0xffffffff810607c8)
 =&gt; try_to_wake_up (0xffffffff8106340a)</tt></pre></div></div>
</div>
</div>
<div class="sect1">
<h2 id="_see_also">SEE ALSO</h2>
<div class="sectionbody">
<div class="paragraph">trace-cmd(1), trace-cmd-report(1), trace-cmd-start(1), trace-cmd-stop(1),
trace-cmd-extract(1), trace-cmd-reset(1), trace-cmd-split(1),
trace-cmd-list(1), trace-cmd-listen(1), trace-cmd-profile(1)</div>
</div>
</div>
<div class="sect1">
<h2 id="_author">AUTHOR</h2>
<div class="sectionbody">
<div class="paragraph">Written by Steven Rostedt, &lt;<a href="mailto:rostedt@goodmis.org">rostedt@goodmis.org</a>&gt;</div>
</div>
</div>
<div class="sect1">
<h2 id="_resources">RESOURCES</h2>
<div class="sectionbody">
<div class="paragraph"><a href="https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/">https://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git/</a></div>
</div>
</div>
<div class="sect1">
<h2 id="_copying">COPYING</h2>
<div class="sectionbody">
<div class="paragraph">Copyright (C) 2010 Red Hat, Inc. Free use of this software is granted under
the terms of the GNU Public License (GPL).</div>
</div>
</div>
</div>
<div id="footnotes"><hr /></div>
<div id="footer">
<div id="footer-text">
Last updated
 2023-06-07 20:21:00 UTC
</div>
</div>
</body>
</html>

${this.title}

Code Editor : trace-cmd-record.1.html