From: Masami Hiramatsu <mhiramat@redhat.com>
To: Frederic Weisbecker <fweisbec@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
lkml <linux-kernel@vger.kernel.org>
Cc: Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Andi Kleen <ak@linux.intel.com>,
Christoph Hellwig <hch@infradead.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>, Jason Baron <jbaron@redhat.com>,
Jim Keniston <jkenisto@us.ibm.com>,
"K.Prasad" <prasad@linux.vnet.ibm.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Peter Zijlstra <peterz@infradead.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Tom Zanussi <tzanussi@gmail.com>,
systemtap <systemtap@sources.redhat.com>,
DLE <dle-develop@lists.sourceforge.net>
Subject: [PATCH tracing/kprobes 0/3] tracing/kprobes: kprobe-tracer updates
Date: Fri, 25 Sep 2009 11:19:52 -0700 [thread overview]
Message-ID: <20090925181952.10157.9975.stgit@omoto> (raw)
Hi Frederic,
Here is a few updates for kprobe-tracer which fix reported bugs and
is for catching up the latest ftrace.
- Use dynamic percpu profiling buffer patch is for catching up
the latest ftrace change.
- Checking the result of create_event_dir() patch improves ftrace
code pointed by Li Zefan (thanks!).
- Add VIA instructions to x86 insn decoder patch fixes decoding
bug reported by Ingo Molnar (thanks!).
Soon after this series, I'll send perf-kprobe patch series.
Thank you,
---
Masami Hiramatsu (3):
tracing/ftrace: Fix to check create_event_dir() when adding new events
x86: Add VIA processor instructions
tracing/kprobes: Use global event profile buffer in kprobe tracer
arch/x86/lib/x86-opcode-map.txt | 8 ++-
kernel/trace/trace_events.c | 29 +++++++---
kernel/trace/trace_kprobe.c | 115 +++++++++++++++++++++++++--------------
3 files changed, 101 insertions(+), 51 deletions(-)
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America), Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
next reply other threads:[~2009-09-25 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 18:19 Masami Hiramatsu [this message]
2009-09-25 18:20 ` [PATCH tracing/kprobes 1/3] tracing/kprobes: Use global event profile buffer in kprobe tracer Masami Hiramatsu
2009-10-17 10:02 ` [tip:perf/probes] tracing/kprobes: Use global event perf buffers " tip-bot for Masami Hiramatsu
2009-09-25 18:20 ` [PATCH tracing/kprobes 2/3] x86: Add VIA processor instructions Masami Hiramatsu
2009-10-17 10:02 ` [tip:perf/probes] x86: Add VIA processor instructions in opcodes decoder tip-bot for Masami Hiramatsu
2009-09-25 18:20 ` [PATCH tracing/kprobes 3/3] tracing/ftrace: Fix to check create_event_dir() when adding new events Masami Hiramatsu
2009-10-03 0:56 ` Frederic Weisbecker
2009-10-17 10:02 ` [tip:perf/probes] " tip-bot for Masami Hiramatsu
2009-09-26 9:08 ` [PATCH tracing/kprobes 0/3] tracing/kprobes: kprobe-tracer updates Steven Rostedt
2009-10-03 0:57 ` Frederic Weisbecker
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=20090925181952.10157.9975.stgit@omoto \
--to=mhiramat@redhat.com \
--cc=ak@linux.intel.com \
--cc=ananth@in.ibm.com \
--cc=dle-develop@lists.sourceforge.net \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=hpa@zytor.com \
--cc=jbaron@redhat.com \
--cc=jkenisto@us.ibm.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=systemtap@sources.redhat.com \
--cc=tzanussi@gmail.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 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.