From: wuzhangjin@gmail.com
To: linux-mips@linux-mips.org, linux-kernel@vger.kernel.org
Cc: Wu Zhangjin <wuzj@lemote.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ralf Baechle <ralf@linux-mips.org>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Nicholas Mc Guire <der.herr@hofr.at>
Subject: [PATCH v1 0/5] mips-specific ftrace support
Date: Fri, 29 May 2009 04:46:08 +0800 [thread overview]
Message-ID: <cover.1243542927.git.wuzj@lemote.com> (raw)
From: Wu Zhangjin <wuzj@lemote.com>
ftrace is a mcount based kernel tracing tool/framework, which is originally
from RT_PREEMPT(http://rt.wiki.kernel.org).
ftrace is short for function tracer, this is its original name, but now, it
becomes a kernel tracing framework, lots of kernel tracers are built on it,
such as irqoff tracer, wakeup tracer and so forth. these tracers are
arch-independent(?), but some of them are arch-dependent, such as the original
ftrace: function tracer, and dynamic function tracer, function graph tracer,
and also, system call tracer.
here is the mips porting of these four arch-dependent tracers, it will enable
the following new kernel config options in linux-mips system.
kernel hacking --->
Tracers -->
[*] Kernel Function Tracer
[*] Kernel Function Graph Tracer
...
[*] Trace syscalls
...
[*] enable/disable ftrace tracepoints dynamically
in reality, because the high-precise timestamp getting function are
arch-dependent, lots of the tracers are arch-dependent. the arch-dependent part
is that: sched_clock, or we say ring_buffer_time_stamp or trace_clock_local
function. to get high-precise timestamp, we can read the MIPS clock counter,
but since it is only 32bit long, so, overflow should be handled carefully.
read the following document, and play with it:
Documentation/trace/ftrace.txt
Wu Zhangjin (5):
mips static function tracer support
mips dynamic function tracer support
mips function graph tracer support
mips specific clock function to get precise timestamp
mips specific system call tracer
arch/mips/Kconfig | 7 +
arch/mips/Makefile | 2 +
arch/mips/include/asm/ftrace.h | 35 ++++-
arch/mips/include/asm/ptrace.h | 2 +
arch/mips/include/asm/reg.h | 5 +
arch/mips/include/asm/syscall.h | 84 ++++++++
arch/mips/include/asm/thread_info.h | 5 +-
arch/mips/kernel/Makefile | 13 ++
arch/mips/kernel/csrc-r4k.c | 2 +-
arch/mips/kernel/entry.S | 2 +-
arch/mips/kernel/ftrace.c | 360 +++++++++++++++++++++++++++++++++++
arch/mips/kernel/ftrace_clock.c | 77 ++++++++
arch/mips/kernel/mcount.S | 185 ++++++++++++++++++
arch/mips/kernel/mips_ksyms.c | 5 +
arch/mips/kernel/ptrace.c | 14 ++-
arch/mips/kernel/scall64-o32.S | 2 +-
arch/mips/kernel/vmlinux.lds.S | 1 +
kernel/trace/ring_buffer.c | 3 +-
kernel/trace/trace_clock.c | 2 +-
scripts/Makefile.build | 1 +
scripts/recordmcount.pl | 32 +++-
21 files changed, 824 insertions(+), 15 deletions(-)
create mode 100644 arch/mips/include/asm/syscall.h
create mode 100644 arch/mips/kernel/ftrace.c
create mode 100644 arch/mips/kernel/ftrace_clock.c
create mode 100644 arch/mips/kernel/mcount.S
reply other threads:[~2009-05-28 20:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=cover.1243542927.git.wuzj@lemote.com \
--to=wuzhangjin@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=der.herr@hofr.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mingo@elte.hu \
--cc=ralf@linux-mips.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=wuzj@lemote.com \
/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).