From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Matt Fleming <mjf@gentoo.org>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Sam Ravnborg <sam@ravnborg.org>,
Jim Radford <radford@galvanix.net>,
Paul Mundt <lethal@linux-sh.org>
Subject: [PATCH 0/5] ftrace: recordmcount for sh and arm, plus permanent disable API
Date: Fri, 21 Nov 2008 15:29:32 -0500 [thread overview]
Message-ID: <20081121202932.281682721@goodmis.org> (raw)
Ingo,
The first two patches are changes to recordmcount.pl that I've tested
to make sure they do not break x86 or PPC. These are changes that are
needed for sh and ARM. I do not include the changes needed in the arch
itself, those need to go through the arch maintainers.
The other patches are for the permanent disabling of the tracer and
ring buffer.
I know you prefered having the ring buffer disable flag be 0 1 -1
for off, on, and disable respectively, but this becomes a problem
to implement safely for all archs. What I did instead was to have
two bits in the flags. On is a simple on/off bit for the users to
use, the other is a set once flag that will permantly disable the
ring buffers once set. This allows me to use the set/clear bit API
that works on all architectures nicely. And I personally find this
easier to understand.
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: tip/devel
Jim Radford (1):
ftrace: mcountrecord.pl for arm
Matt Fleming (1):
ftrace: Specify $alignment for sh architecture
Steven Rostedt (3):
ring-buffer: add tracing_off_permanent
ftrace: add ftrace_off_permanent
trace: fix compiler warning in branch profiler
----
include/linux/ftrace.h | 2 +
include/linux/ring_buffer.h | 1 +
kernel/trace/ring_buffer.c | 79 ++++++++++++++++++++++++++++++++++++-------
kernel/trace/trace.c | 15 ++++++++
kernel/trace/trace_branch.c | 10 +++---
scripts/recordmcount.pl | 11 +++++-
6 files changed, 98 insertions(+), 20 deletions(-)
next reply other threads:[~2008-11-21 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 20:29 Steven Rostedt [this message]
2008-11-21 20:29 ` [PATCH 1/5] ftrace: Specify $alignment for sh architecture Steven Rostedt
2008-11-21 20:29 ` [PATCH 2/5] ftrace: mcountrecord.pl for arm Steven Rostedt
2008-11-21 20:29 ` [PATCH 3/5] ring-buffer: add tracing_off_permanent Steven Rostedt
2008-11-21 20:29 ` [PATCH 4/5] ftrace: add ftrace_off_permanent Steven Rostedt
2008-11-21 20:29 ` [PATCH 5/5] trace: fix compiler warning in branch profiler Steven Rostedt
2008-11-23 10:51 ` [PATCH 0/5] ftrace: recordmcount for sh and arm, plus permanent disable API 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=20081121202932.281682721@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mingo@elte.hu \
--cc=mjf@gentoo.org \
--cc=radford@galvanix.net \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.