From d100faf49cf77665f920db9a2585ba7c0e13c520 Mon Sep 17 00:00:00 2001
From: Jan Altenberg <jan@linutronix.de>
Date: Thu, 10 Feb 2011 11:47:44 +0100
Subject: Mention trace_printk and ftrace specific kernel parameters

---
 .../kernel-tracing/pres_kernel-tracing_en.tex      | 29 ++++++++++++++++++++++
 1 file changed, 29 insertions(+)

(limited to 'kernel-devel/kernel-tracing')

diff --git a/kernel-devel/kernel-tracing/pres_kernel-tracing_en.tex b/kernel-devel/kernel-tracing/pres_kernel-tracing_en.tex
index 11c2f5f..08a5d03 100644
--- a/kernel-devel/kernel-tracing/pres_kernel-tracing_en.tex
+++ b/kernel-devel/kernel-tracing/pres_kernel-tracing_en.tex
@@ -131,6 +131,35 @@ ls-4579    3dN...    5us : _raw_spin_unlock_irqrestore <-try_to_wake_up
 \end{verbatim}
 \end{frame}
 
+\begin{frame}[fragile]
+\frametitle{trace\_printk()}
+\begin{itemize}
+\item trace\_printk() can be used to write messages to the tracing ring buffer
+\item Usage is similar to printk()
+\end{itemize}
+\end{frame}
+
+\begin{frame}[fragile]
+\frametitle{Tracing related kernel parameters}
+\begin{verbatim}
+ftrace=
+\end{verbatim}
+Set and start specified tracer as early as possible.
+\begin{verbatim}
+ftrace_dump_on_oops[=orig_cpu]
+\end{verbatim}
+Dump the tracing ring buffer if an Oops occurs. Using orig\_cpu it will only
+dump the buffer of the CPU which triggered the Oops.
+\begin{verbatim}
+ftrace_filter=
+\end{verbatim}
+Only trace specific functions.
+\begin{verbatim}
+ftrace_notrace=
+\end{verbatim}
+Don't trace specific functions.
+\end{frame}
+
 \section{trace-cmd}
 
 \begin{frame}
-- 
cgit v1.2.3