From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Masami Hiramatsu <mhiramat@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mike Galbraith <efault@gmx.de>, Paul Mackerras <paulus@samba.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Christoph Hellwig <hch@infradead.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
Jim Keniston <jkenisto@us.ibm.com>,
"Frank Ch . Eigler" <fche@redhat.com>,
Li Zefan <lizf@cn.fujitsu.com>
Subject: Re: [GIT PULL] tracing/kprobes: Syntax updates, introduce perf probe
Date: Tue, 13 Oct 2009 12:26:18 +0200 [thread overview]
Message-ID: <20091013102618.GA18794@elte.hu> (raw)
In-Reply-To: <20091013074838.GA5076@nowhere>
* Frederic Weisbecker <fweisbec@gmail.com> wrote:
> On Tue, Oct 13, 2009 at 08:13:23AM +0200, Ingo Molnar wrote:
> >
> > * Frederic Weisbecker <fweisbec@gmail.com> wrote:
> >
> > > Ingo,
> > >
> > > I've tested a little this set and it seems to work well. I can't test
> > > the C expression parser (need some libdwarf cross-version
> > > compatiblity), but I can create kprobes via low-level parameters, then
> > > launch perf record and perf trace successfully. I'll need to update
> > > perf trace to handle variables that start with '$' characters though.
> > >
> > > Anyway, it's still unstable but I guess pulling it would help Masami
> > > to continue without the need to handle the whole batch.
> > >
> > > Please pull the tracing/kprobes branch that can be found at:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
> > > tracing/kprobes
> >
> > Pulled, thanks Frederic.
> >
> > > Documentation/trace/kprobetrace.txt | 27 +-
> > > kernel/trace/trace_kprobe.c | 160 +++++---
> > > tools/perf/Makefile | 10 +
> > > tools/perf/builtin-probe.c | 386 +++++++++++++++++++
> > > tools/perf/builtin.h | 1 +
> > > tools/perf/perf.c | 1 +
> > > tools/perf/util/probe-finder.c | 690 +++++++++++++++++++++++++++++++++++
> > > tools/perf/util/probe-finder.h | 70 ++++
> > > 8 files changed, 1271 insertions(+), 74 deletions(-)
> > > create mode 100644 tools/perf/builtin-probe.c
> > > create mode 100644 tools/perf/util/probe-finder.c
> > > create mode 100644 tools/perf/util/probe-finder.h
> >
> > Hm, there's no x86 decoder change here - does this lot fixes the
> > instruction decoder bug i reported some time ago? That is which keeps
> > tracing/kprobes out of tip:master.
> >
> > Ingo
>
>
> Not yet, I hope it's part of the last family of instruction set we are
> missing.
ok.
We dont want topics to not be in tip:master for too long - we dont grow
conflict resolutions nor does it get tested widely.
Ingo
prev parent reply other threads:[~2009-10-13 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 22:25 [GIT PULL] tracing/kprobes: Syntax updates, introduce perf probe Frederic Weisbecker
2009-10-12 22:25 ` [PATCH] kill-the-bkl/reiserfs: fix reiserfs lock to cpu_add_remove_lock dependency Frederic Weisbecker
2009-10-12 22:30 ` Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 1/7] tracing/kprobes: Add $ prefix to special variables Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 2/7] tracing/kprobes: Remove '$ra' special variable Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 3/7] tracing/kprobes: Make special variable names more self-explainable Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 4/7] tracing/kprobes: Avoid field name confliction Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 5/7] tracing/kprobes: Robustify fixed field names against variable field names conflicts Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 6/7] perf: Add perf probe subcommand, a kprobe-event setup helper Frederic Weisbecker
2009-10-12 22:25 ` [PATCH 7/7] perf probe: Add perf probe command support without libdwarf Frederic Weisbecker
2009-10-13 6:13 ` [GIT PULL] tracing/kprobes: Syntax updates, introduce perf probe Ingo Molnar
2009-10-13 6:22 ` Ingo Molnar
2009-10-13 13:00 ` Masami Hiramatsu
2009-10-13 7:48 ` Frederic Weisbecker
2009-10-13 10:26 ` Ingo Molnar [this message]
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=20091013102618.GA18794@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=ananth@in.ibm.com \
--cc=efault@gmx.de \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jkenisto@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mhiramat@redhat.com \
--cc=paulus@samba.org \
--cc=rostedt@goodmis.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox