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-report.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-REPORT(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-REPORT(1) Manual Page
</h1>
<h2>NAME</h2>
<div class="sectionbody">
trace-cmd-report -
 show in ASCII a trace created by trace-cmd record

</div>
</div>
<div id="content">
<div class="sect1">
<h2 id="_synopsis">SYNOPSIS</h2>
<div class="sectionbody">
<div class="paragraph">trace-cmd report [OPTIONS] [input-file]</div>
</div>
</div>
<div class="sect1">
<h2 id="_description">DESCRIPTION</h2>
<div class="sectionbody">
<div class="paragraph">The trace-cmd(1) report command will output a human readable report of a trace
created by trace-cmd record.</div>
</div>
</div>
<div class="sect1">
<h2 id="_options">OPTIONS</h2>
<div class="sectionbody">
<div class="dlist"><dl>
<dt class="hdlist1">
-i input-file
</dt>
<dd>

 By default, trace-cmd report will read the file trace.dat. But the -i
 option open up the given input-file instead. Note, the input file may
 also be specified as the last item on the command line.

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

 This outputs the endianess of the file. trace-cmd report is smart enough
 to be able to read big endian files on little endian machines, and vise
 versa.

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

 This outputs the list of all functions that have been mapped in the trace.dat file.
 Note, this list may contain functions that may not appear in the trace, as
 it is the list of mappings to translate function addresses into function names.

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

 This outputs the list of "trace_printk()" data. The raw trace data points
 to static pointers in the kernel. This must be stored in the trace.dat
 file.

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

 This lists the possible events in the file (but this list is not
 necessarily the list of events in the file).

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

 This will list the event formats that are stored in the trace.dat file.

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

 This will print events that match the given regex. If a colon is specified,
 then the characters before the colon will be used to match the system and
 the characters after the colon will match the event.

<div class="literalblock">
<div class="content">
<pre><code>trace-cmd report --event sys:read</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The above will only match events where the system name contains "sys"
and the event name contains "read".</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>trace-cmd report --event read</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The above will match all events that contain "read" in its name. Also it
may list all events of a system that contains "read" as well.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--check-events
</dt>
<dd>

 This will parse the event format strings that are stored in the trace.dat
 file and return whether the formats can be parsed correctly. It will load
 plugins unless -N is specified.

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

 Print the full timestamp. The timestamps in the data file are usually
 recorded to the nanosecond. But the default display of the timestamp
 is only to the microsecond. To see the full timestamp, add the -t option.

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

 Add a filter to limit what events are displayed. Filters defined
 after an input file (specified with -i) only apply to that
 input file. Filters provided before any input file is given are
 considered global and apply to all input files.

<div class="literalblock">
<div class="content">
<pre><code>The format of the filter is:</code></pre>
</div></div>
</dd>
</dl></div>
<div class="listingblock">
<div class="content">
<pre><tt> &lt;events&gt; ':' &lt;filter&gt;
 &lt;events&gt; = SYSTEM'/'EVENT | SYSTEM | EVENT | &lt;events&gt; ',' &lt;events&gt;
 &lt;filter&gt; = EVENT_FIELD &lt;op&gt; &lt;value&gt; | &lt;filter&gt; '&amp;&amp;' &lt;filter&gt; |
 &lt;filter&gt; '||' &lt;filter&gt; | '(' &lt;filter&gt; ')' | '!' &lt;filter&gt;
 &lt;op&gt; = '==' | '!=' | '&gt;=' | '&lt;=' | '&gt;' | '&lt;' | '&amp;' | '|' | '^' |
 '+' | '-' | '*' | '/' | '%'
 &lt;value&gt; = NUM | STRING | EVENT_FIELD</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>SYSTEM is the name of the system to filter on. If the EVENT is left out,
then it applies to all events under the SYSTEM. If only one string is used
without the '/' to deliminate between SYSTEM and EVENT, then the filter
will be applied to all systems and events that match the given string.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Whitespace is ignored, such that "sched:next_pid==123" is equivalent to
"sched : next_pid == 123".</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>STRING is defined with single or double quotes (single quote must end with
single quote, and double with double). Whitespace within quotes are not
ignored.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The representation of a SYSTEM or EVENT may also be a regular expression
as defined by 'regcomp(3)'.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The EVENT_FIELD is the name of the field of an event that is being
filtered. If the event does not contain the EVENT_FIELD, that part of the
equation will be considered false.</code></pre>
</div></div>
<div class="listingblock">
<div class="content">
<pre><tt> -F 'sched : bogus == 1 || common_pid == 2'</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>The "bogus == 1" will always evaluate to FALSE because no event has a
field called "bogus", but the "common_pid == 2" will still be evaluated
since all events have the field "common_pid". Any "sched" event that was
traced by the process with the PID of 2 will be shown.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Note, the EVENT_FIELD is the field name as shown by an events format
(as displayed with *--events*), and not what is found in the output.
If the output shows "ID:foo" but the field that "foo" belongs to was
called "name" in the event format, then "name" must be used in the filter.
The same is true about values. If the value that is displayed is converted
by to a string symbol, the filter checks the original value and not the
value displayed. For example, to filter on all tasks that were in the
running state at a context switch:</code></pre>
</div></div>
<div class="listingblock">
<div class="content">
<pre><tt> -F 'sched/sched_switch : prev_state==0'</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>Although the output displays 'R', having 'prev_stat=="R"' will not work.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Note: You can also specify 'COMM' as an EVENT_FIELD. This will use the
task name (or comm) of the record to compare. For example, to filter out
all of the "trace-cmd" tasks:</code></pre>
</div></div>
<div class="listingblock">
<div class="content">
<pre><tt> -F '.*:COMM != "trace-cmd"'</tt></pre></div></div>
<div class="dlist"><dl>
<dt class="hdlist1">
-I
</dt>
<dd>

 Do not print events where the HARDIRQ latency flag is set.
 This will filter out most events that are from interrupt context.
 Note, it may not filter out function traced functions that are
 in interrupt context but were called before the kernel "in interrupt"
 flag was set.

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

 Do not print events where the SOFTIRQ latency flag is set.
 This will filter out most events that are from soft interrupt context.

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

 This causes the following filters of -F to filter out the matching
 events.

</dd>
</dl></div>
<div class="listingblock">
<div class="content">
<pre><tt> -v -F 'sched/sched_switch : prev_state == 0'</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>Will not display any sched_switch events that have a prev_state of 0.
Removing the *-v* will only print out those events.</code></pre>
</div></div>
<div class="dlist"><dl>
<dt class="hdlist1">
-T
</dt>
<dd>

 Test the filters of -F. After processing a filter string, the
 resulting filter will be displayed for each event. This is useful
 for using a filter for more than one event where a field may not
 exist in all events. Also it can be used to make sure there are no
 misspelled event field names, as they will simply be ignored.
 -T is ignored if -F is not specified.

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

 Show verbose messages (see --verbose but only for the numbers)

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

 This will not load system wide plugins. It loads "local only". That is
 what it finds in the ~/.trace-cmd/plugins directory.

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

 This will not load any plugins.

</dd>
<dt class="hdlist1">
-n event-re
</dt>
<dd>

 This will cause all events that match the option to ignore any registered
 handler (by the plugins) to print the event. The normal event will be printed
 instead. The event-re is a regular expression as defined by regcomp(3).

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

 With the --profile option, "trace-cmd report" will process all the events
 first, and then output a format showing where tasks have spent their time
 in the kernel, as well as where they are blocked the most, and where wake up
 latencies are.

<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.

<div class="literalblock">
<div class="content">
<pre><code>See trace-cmd-profile(1) for format.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
-R
</dt>
<dd>

 This will show the events in "raw" format. That is, it will ignore the event&#8217;s
 print formatting and just print the contents of each field.

</dd>
<dt class="hdlist1">
-r event-re
</dt>
<dd>

 This will cause all events that match the option to print its raw fields.
 The event-re is a regular expression as defined by regcomp(3).

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

 This adds a "latency output" format. Information about interrupts being
 disabled, soft irq being disabled, the "need_resched" flag being set,
 preempt count, and big kernel lock are all being recorded with every
 event. But the default display does not show this information. This option
 will set display this information with 6 characters. When one of the
 fields is zero or N/A a '.\' is shown.

</dd>
</dl></div>
<div class="listingblock">
<div class="content">
<pre><tt> &lt;idle&gt;-0 0d.h1. 106467.859747: function: ktime_get &lt;-- tick_check_idle</tt></pre></div></div>
<div class="literalblock">
<div class="content">
<pre><code>The 0d.h1. denotes this information.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>It starts with a number. This represents the CPU number that the event occurred
on.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The second character is one of the following:</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'d' - Interrupts are disabled
'.' - Interrupts are enabled
'X' - Has flags that are not yet known by trace-cmd</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The third character is the "need rescheduling" flag.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'N' - A schedule is set to take place
'.' - No scheduling is set</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The fourth character represents the context the event was in when it triggered</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>'h' - Hard interrupt context
's' - Soft interrupt context
'H' - Hard interrupt context that interrupted a soft interrupt
'.' - Normal context</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The next is a number (should be less than 10), that represents the preemption
depth (the number of times preempt_disable() is called without preempt_enable()).
'.' means preemption is enabled.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>On some systems, "migrate disable" may exist, in which case a number will be
shown for that, or '.' meaning migration is enabled.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>If lockdep in enabled on the system, then the number represents the depth of
locks that are held when the event triggered. '.' means no locks are held.</code></pre>
</div></div>
<div class="dlist"><dl>
<dt class="hdlist1">
-w
</dt>
<dd>

 If both the sched_switch and sched_wakeup events are enabled, then
 this option will report the latency between the time the task was first
 woken, and the time it was scheduled in.

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

 Quiet non critical warnings.

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

 Pass options to the trace-cmd plugins that are loaded.

<div class="literalblock">
<div class="content">
<pre><code>-O plugin:var=value</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The 'plugin:' and '=value' are optional. Value may be left off for options
that are boolean. If the 'plugin:' is left off, then any variable that matches
in all plugins will be set.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Example: -O fgraph:tailprint</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--cpu &lt;cpu list&gt;
</dt>
<dd>

 List of CPUs, separated by "," or ":", used for filtering the events.
 A range of CPUs can be specified using "cpuX-cpuY" notation, where all CPUs
 in the range between cpuX and cpuY will be included in the list. The order
 of CPUs in the list must be from lower to greater.

<div class="literalblock">
<div class="content">
<pre><code>Example: "--cpu 0,3" - show events from CPUs 0 and 3
 "--cpu 2-4" - show events from CPUs 2, 3 and 4</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--cpus
</dt>
<dd>

 List the CPUs that have data in the trace file then exit.

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

 Show the timestamp of the first event of all CPUs that have data.

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

 Show the timestamp of the last event of all CPUs that have data.

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

 If the trace.dat file recorded the final stats (outputed at the end of record)
 the --stat option can be used to retrieve them.

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

 If the trace.dat file recorded uname during the run, this will retrieve that
 information.

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

 If the trace.dat file recorded the version of the executable used to create
 it, report that version.

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

 Add (or subtract if negative) an offset for all timestamps of the previous
 data file specified with -i. This is useful to merge sort multiple trace.dat
 files where the difference in the timestamp is known. For example if a trace
 is done on a virtual guest, and another trace is done on the host. If the
 host timestamp is 1000 units ahead of the guest, the following can be done:

<div class="literalblock">
<div class="content">
<pre><code>trace-cmd report -i host.dat --ts-offset -1000 -i guest.dat</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>This will subtract 1000 timestamp units from all the host events as it merges
with the guest.dat events. Note, the units is for the raw units recorded in
the trace. If the units are nanoseconds, the addition (or subtraction) from
the offset will be nanoseconds even if the displayed units are microseconds.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--ts2secs HZ
</dt>
<dd>

 Convert the current clock source into a second (nanosecond resolution)
 output. When using clocks like x86-tsc, if the frequency is known,
 by passing in the clock frequency, this will convert the time to seconds.

<div class="literalblock">
<div class="content">
<pre><code>This option affects any trace.dat file given with *-i* proceeding it.
If this option comes before any *-i* option, then that value becomes
the default conversion for all other trace.dat files. If another
--ts2secs option appears after a *-i* trace.dat file, than that option
will override the default value.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>Example: On a 3.4 GHz machine</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>trace-cmd record -p function -C x86-tsc</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>trace-cmd report --ts2ns 3400000000</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The report will convert the cycles timestamps into a readable second
display. The default display resolution is microseconds, unless *-t*
is used.</code></pre>
</div></div>
<div class="literalblock">
<div class="content">
<pre><code>The value of --ts-offset must still be in the raw timestamp units, even
with this option. The offset will be converted as well.</code></pre>
</div></div>
</dd>
<dt class="hdlist1">
--ts-diff
</dt>
<dd>

 Show the time differences between events. The difference will appear in
 parenthesis just after the timestamp.

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

 Make sure no timestamp goes backwards, and if it does, print out a warning
 message of the fact.

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

 Ignore converting the timestamps to the date set by trace-cmd record(3) --date option.

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

 Display raw timestamps, without any corrections.

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

 Display timestamps aligned to the first event.

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

 Set the log level. Supported log levels are "none", "crit", "err", "warn",
 "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 report --verbose=warning</code></pre>
</div></div>
</dd>
</dl></div>
</div>
</div>
<div class="sect1">
<h2 id="_examples">EXAMPLES</h2>
<div class="sectionbody">
<div class="paragraph">Using a trace.dat file that was created with:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd record -p function -e all sleep 5</tt></pre></div></div>
<div class="paragraph">The default report shows:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd report
 trace-cmd-16129 [002] 158126.498411: function: __mutex_unlock_slowpath &lt;-- mutex_unlock
 trace-cmd-16131 [000] 158126.498411: kmem_cache_alloc: call_site=811223c5 ptr=0xffff88003ecf2b40 bytes_req=272 bytes_alloc=320 gfp_flags=GFP_KERNEL|GFP_ZERO
 trace-cmd-16130 [003] 158126.498411: function: do_splice_to &lt;-- sys_splice
 sleep-16133 [001] 158126.498412: function: inotify_inode_queue_event &lt;-- vfs_write
 trace-cmd-16129 [002] 158126.498420: lock_release: 0xffff88003f1fa4f8 &amp;sb-&gt;s_type-&gt;i_mutex_key
 trace-cmd-16131 [000] 158126.498421: function: security_file_alloc &lt;-- get_empty_filp
 sleep-16133 [001] 158126.498422: function: __fsnotify_parent &lt;-- vfs_write
 trace-cmd-16130 [003] 158126.498422: function: rw_verify_area &lt;-- do_splice_to
 trace-cmd-16131 [000] 158126.498424: function: cap_file_alloc_security &lt;-- security_file_alloc
 trace-cmd-16129 [002] 158126.498425: function: syscall_trace_leave &lt;-- int_check_syscall_exit_work
 sleep-16133 [001] 158126.498426: function: inotify_dentry_parent_queue_event &lt;-- vfs_write
 trace-cmd-16130 [003] 158126.498426: function: security_file_permission &lt;-- rw_verify_area
 trace-cmd-16129 [002] 158126.498428: function: audit_syscall_exit &lt;-- syscall_trace_leave
[...]</tt></pre></div></div>
<div class="paragraph">To see everything but the function traces:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd report -v -F 'function'
 trace-cmd-16131 [000] 158126.498411: kmem_cache_alloc: call_site=811223c5 ptr=0xffff88003ecf2b40 bytes_req=272 bytes_alloc=320 gfp_flags=GFP_KERNEL|GFP_ZERO
 trace-cmd-16129 [002] 158126.498420: lock_release: 0xffff88003f1fa4f8 &amp;sb-&gt;s_type-&gt;i_mutex_key
 trace-cmd-16130 [003] 158126.498436: lock_acquire: 0xffffffff8166bf78 read all_cpu_access_lock
 trace-cmd-16131 [000] 158126.498438: lock_acquire: 0xffff88003df5b520 read &amp;fs-&gt;lock
 trace-cmd-16129 [002] 158126.498446: kfree: call_site=810a7abb ptr=0x0
 trace-cmd-16130 [003] 158126.498448: lock_acquire: 0xffff880002250a80 &amp;per_cpu(cpu_access_lock, cpu)
 trace-cmd-16129 [002] 158126.498450: sys_exit_splice: 0xfffffff5
 trace-cmd-16131 [000] 158126.498454: lock_release: 0xffff88003df5b520 &amp;fs-&gt;lock
 sleep-16133 [001] 158126.498456: kfree: call_site=810a7abb ptr=0x0
 sleep-16133 [001] 158126.498460: sys_exit_write: 0x1
 trace-cmd-16130 [003] 158126.498462: kmalloc: call_site=810bf95b ptr=0xffff88003dedc040 bytes_req=24 bytes_alloc=32 gfp_flags=GFP_KERNEL|GFP_ZERO

</tt></pre></div></div>
<div class="paragraph">To see only the kmalloc calls that were greater than 1000 bytes:</div>
<div class="listingblock">
<div class="content">
<pre><tt> #trace-cmd report -F 'kmalloc: bytes_req &gt; 1000'
 &lt;idle&gt;-0 [000] 158128.126641: kmalloc: call_site=81330635 ptr=0xffff88003c2fd000 bytes_req=2096 bytes_alloc=4096 gfp_flags=GFP_ATOMIC

</tt></pre></div></div>
<div class="paragraph">To see wakeups and sched switches that left the previous task in the running
state:</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd report -F 'sched: prev_state == 0 || (success == 1)'
 trace-cmd-16132 [002] 158126.499951: sched_wakeup: comm=trace-cmd pid=16129 prio=120 success=1 target_cpu=002
 trace-cmd-16132 [002] 158126.500401: sched_switch: prev_comm=trace-cmd prev_pid=16132 prev_prio=120 prev_state=R ==&gt; next_comm=trace-cmd next_pid=16129 next_prio=120
 &lt;idle&gt;-0 [003] 158126.500585: sched_wakeup: comm=trace-cmd pid=16130 prio=120 success=1 target_cpu=003
 &lt;idle&gt;-0 [003] 158126.501241: sched_switch: prev_comm=swapper prev_pid=0 prev_prio=120 prev_state=R ==&gt; next_comm=trace-cmd next_pid=16130 next_prio=120
 trace-cmd-16132 [000] 158126.502475: sched_wakeup: comm=trace-cmd pid=16131 prio=120 success=1 target_cpu=000
 trace-cmd-16131 [002] 158126.506516: sched_wakeup: comm=trace-cmd pid=16129 prio=120 success=1 target_cpu=002
 &lt;idle&gt;-0 [003] 158126.550110: sched_switch: prev_comm=swapper prev_pid=0 prev_prio=120 prev_state=R ==&gt; next_comm=trace-cmd next_pid=16130 next_prio=120
 trace-cmd-16131 [003] 158126.570243: sched_wakeup: comm=trace-cmd pid=16129 prio=120 success=1 target_cpu=003
 trace-cmd-16130 [002] 158126.618202: sched_switch: prev_comm=trace-cmd prev_pid=16130 prev_prio=120 prev_state=R ==&gt; next_comm=yum-updatesd next_pid=3088 next_prio=1 20
 trace-cmd-16129 [003] 158126.622379: sched_wakeup: comm=trace-cmd pid=16131 prio=120 success=1 target_cpu=003
 trace-cmd-16129 [000] 158126.649287: sched_wakeup: comm=trace-cmd pid=16131 prio=120 success=1 target_cpu=000</tt></pre></div></div>
<div class="paragraph">The above needs a little explanation. The filter specifies the "sched"
subsystem, which includes both sched_switch and sched_wakeup events. Any event
that does not have the format field "prev_state" or "success", will evaluate
those expressions as FALSE, and will not produce a match. Using "||" will have
the "prev_state" test happen for the "sched_switch" event and the "success"
test happen for the "sched_wakeup" event.</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd report -w -F 'sched_switch, sched_wakeup.*'
[...]
 trace-cmd-16130 [003] 158131.580616: sched_wakeup: comm=trace-cmd pid=16131 prio=120 success=1 target_cpu=003
 trace-cmd-16129 [000] 158131.581502: sched_switch: prev_comm=trace-cmd prev_pid=16129 prev_prio=120 prev_state=S ==&gt; next_comm=trace-cmd next_pid=16131 next_prio=120 Latency: 885.901 usecs
 trace-cmd-16131 [000] 158131.582414: sched_wakeup: comm=trace-cmd pid=16129 prio=120 success=1 target_cpu=000
 trace-cmd-16132 [001] 158131.583219: sched_switch: prev_comm=trace-cmd prev_pid=16132 prev_prio=120 prev_state=S ==&gt; next_comm=trace-cmd next_pid=16129 next_prio=120 Latency: 804.809 usecs
 sleep-16133 [002] 158131.584121: sched_wakeup: comm=trace-cmd pid=16120 prio=120 success=1 target_cpu=002
 trace-cmd-16129 [001] 158131.584128: sched_wakeup: comm=trace-cmd pid=16132 prio=120 success=1 target_cpu=001
 sleep-16133 [002] 158131.584275: sched_switch: prev_comm=sleep prev_pid=16133 prev_prio=120 prev_state=R ==&gt; next_comm=trace-cmd next_pid=16120 next_prio=120 Latency: 153.915 usecs
 trace-cmd-16130 [003] 158131.585284: sched_switch: prev_comm=trace-cmd prev_pid=16130 prev_prio=120 prev_state=S ==&gt; next_comm=trace-cmd next_pid=16132 next_prio=120 Latency: 1155.677 usecs

Average wakeup latency: 26626.656 usecs</tt></pre></div></div>
<div class="paragraph">The above trace produces the wakeup latencies of the tasks. The "sched_switch"
event reports each individual latency after writing the event information.
At the end of the report, the average wakeup latency is reported.</div>
<div class="listingblock">
<div class="content">
<pre><tt> # trace-cmd report -w -F 'sched_switch, sched_wakeup.*: prio &lt; 100 || next_prio &lt; 100'
 &lt;idle&gt;-0 [003] 158131.516753: sched_wakeup: comm=ksoftirqd/3 pid=13 prio=49 success=1 target_cpu=003
 &lt;idle&gt;-0 [003] 158131.516855: sched_switch: prev_comm=swapper prev_pid=0 prev_prio=120 prev_state=R ==&gt; next_comm=ksoftirqd/3 next_pid=13 next_prio=49 Latency: 101.244 usecs
 &lt;idle&gt;-0 [003] 158131.533781: sched_wakeup: comm=ksoftirqd/3 pid=13 prio=49 success=1 target_cpu=003
 &lt;idle&gt;-0 [003] 158131.533897: sched_switch: prev_comm=swapper prev_pid=0 prev_prio=120 prev_state=R ==&gt; next_comm=ksoftirqd/3 next_pid=13 next_prio=49 Latency: 115.608 usecs
 &lt;idle&gt;-0 [003] 158131.569730: sched_wakeup: comm=ksoftirqd/3 pid=13 prio=49 success=1 target_cpu=003
 &lt;idle&gt;-0 [003] 158131.569851: sched_switch: prev_comm=swapper prev_pid=0 prev_prio=120 prev_state=R ==&gt; next_comm=ksoftirqd/3 next_pid=13 next_prio=49 Latency: 121.024 usecs

Average wakeup latency: 110.021 usecs</tt></pre></div></div>
<div class="paragraph">The above version will only show the wakeups and context switches of Real Time
tasks. The prio used inside the kernel starts at 0 for highest priority.
That is prio 0 is equivalent to user space real time priority 99, and
priority 98 is equivalent to user space real time priority 1.
Prios less than 100 represent Real Time tasks.</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-record(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-report.1.html