linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masami Hiramatsu <mhiramat@kernel.org>
To: Steven Rostedt <rostedt@goodmis.org>, Jonathan Corbet <corbet@lwn.net>
Cc: mhiramat@kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: [PATCH 6/6] Documentation: tracing: boot: Add an example of tracing function-calls
Date: Mon, 31 Aug 2020 21:46:19 +0900	[thread overview]
Message-ID: <159887797965.1330989.8398347951884039748.stgit@devnote2> (raw)
In-Reply-To: <159887792384.1330989.5993224243767476896.stgit@devnote2>

Add an example of tracing function calls on a specific function.

Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
---
 Documentation/trace/boottime-trace.rst |   20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/Documentation/trace/boottime-trace.rst b/Documentation/trace/boottime-trace.rst
index 1341b449acaa..c216f5695ae2 100644
--- a/Documentation/trace/boottime-trace.rst
+++ b/Documentation/trace/boottime-trace.rst
@@ -168,6 +168,26 @@ is for tracing functions starting with "user\_", and others tracing
 The instance node also accepts event nodes so that each instance
 can customize its event tracing.
 
+With the trigger action and kprobes, you can trace function-graph while
+a function is called. For example, this will trace all function calls in
+the pci_proc_init()::
+
+  ftrace {
+        tracing_on = 0
+        tracer = function_graph
+        event.kprobes {
+                start_event {
+                        probes = "pci_proc_init"
+                        actions = "traceon"
+                }
+                end_event {
+                        probes = "pci_proc_init%return"
+                        actions = "traceoff"
+                }
+        }
+  }
+
+
 This boot-time tracing also supports ftrace kernel parameters via boot
 config.
 For example, following kernel parameters::


      parent reply	other threads:[~2020-08-31 12:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-31 12:45 [PATCH 0/6] tracing/boot: Add new options for tracing specific period Masami Hiramatsu
2020-08-31 12:45 ` [PATCH 1/6] kprobes: tracing/kprobes: Fix to kill kprobes on initmem after boot Masami Hiramatsu
2020-08-31 16:25   ` kernel test robot
2020-09-01  6:27     ` Masami Hiramatsu
2020-08-31 12:45 ` [PATCH 2/6] tracing/boot: Add per-instance tracing_on option support Masami Hiramatsu
2020-08-31 12:45 ` [PATCH 3/6] Documentation: tracing: Add tracing_on option to boot-time tracer Masami Hiramatsu
2020-08-31 12:46 ` [PATCH 4/6] tracing/kprobes: Support perf-style return probe Masami Hiramatsu
2020-08-31 12:46 ` [PATCH 5/6] Documentation: tracing: Add %return suffix description Masami Hiramatsu
2020-08-31 18:50   ` Randy Dunlap
2020-08-31 22:27     ` Masami Hiramatsu
2020-09-01  5:46       ` Masami Hiramatsu
2020-08-31 12:46 ` Masami Hiramatsu [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=159887797965.1330989.8398347951884039748.stgit@devnote2 \
    --to=mhiramat@kernel.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).