From: Brian Norris <computersforpeace@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: <linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
Brian Norris <computersforpeace@gmail.com>,
Jonathan Corbet <corbet@lwn.net>, Li Zefan <lizf@cn.fujitsu.com>
Subject: [PATCH] doc: clarify that trace_events= takes a comma-separated list
Date: Mon, 23 May 2016 13:08:31 -0700 [thread overview]
Message-ID: <1464034111-25340-1-git-send-email-computersforpeace@gmail.com> (raw)
It took me browsing through the source code to determine that I was,
indeed, using the wrong delimiter in my command lines. So I might as
well document it for the next person.
Signed-off-by: Brian Norris <computersforpeace@gmail.com>
---
Documentation/kernel-parameters.txt | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 5349363b603c..594bf50b8f81 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -3994,7 +3994,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
trace_event=[event-list]
[FTRACE] Set and start specified trace events in order
- to facilitate early boot debugging.
+ to facilitate early boot debugging. The event-list is a
+ comma separated list of trace events to enable, as if
+ you were to append the event(s) to
+
+ /sys/kernel/debug/tracing/set_event
+
See also Documentation/trace/events.txt
trace_options=[option-list]
--
2.8.0.rc3.226.g39d4020
next reply other threads:[~2016-05-23 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-23 20:08 Brian Norris [this message]
2016-05-23 20:25 ` [PATCH] doc: clarify that trace_events= takes a comma-separated list Steven Rostedt
2016-05-23 20:32 ` Brian Norris
2016-05-23 20:37 ` [PATCH v2] " Brian Norris
2016-05-23 20:54 ` Steven Rostedt
2016-05-23 20:56 ` Jonathan Corbet
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=1464034111-25340-1-git-send-email-computersforpeace@gmail.com \
--to=computersforpeace@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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