From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org
Subject: [PATCH 0/1] ring-buffer: disable tracing switch
Date: Tue, 11 Nov 2008 15:06:01 -0500 [thread overview]
Message-ID: <20081111200601.147669239@goodmis.org> (raw)
Stephen and Ingo,
I've been pressured into making this patch for mainline. It is a low risk
patch, but I would like to get it into linux-next.
This patch adds a way for a kernel developer to stop all tracers from
within the kernel and restart it from userspace. The previous APIs that
allowed for kernel stopping the tracer did not allow for userspace to
restart. This was mainly because the stopping could be for areas that
are dangerous to be tracing, and allowing userspace to start them could
risk the system stability.
This switch is made to let userspace interact with the kernel space
in starting and stopping tracers.
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: devel
Steven Rostedt (1):
ring-buffer: buffer record on/off switch
----
include/linux/ring_buffer.h | 3 +
kernel/trace/ftrace.c | 8 +---
kernel/trace/ring_buffer.c | 101 +++++++++++++++++++++++++++++++++++++++++++
3 files changed, 106 insertions(+), 6 deletions(-)
--
next reply other threads:[~2008-11-11 20:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 20:06 Steven Rostedt [this message]
2008-11-11 20:06 ` [PATCH 1/1] ring-buffer: buffer record on/off switch Steven Rostedt
2008-11-11 20:56 ` Andrew Morton
2008-11-11 21:04 ` Steven Rostedt
2008-11-11 21:08 ` Ingo Molnar
2008-11-12 14:11 ` Andy Whitcroft
2008-11-11 21:06 ` Steven Rostedt
2008-11-12 12:51 ` Pavel Machek
2008-11-11 20:36 ` [PATCH 0/1] ring-buffer: disable tracing switch Ingo Molnar
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=20081111200601.147669239@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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).