From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Mike Galbraith <efault@gmx.de>,
Brice Goglin <Brice.Goglin@inria.fr>
Subject: [GIT PULL v2] perf tools: Factorize common code
Date: Wed, 12 Aug 2009 12:48:29 +0200 [thread overview]
Message-ID: <1250074112-15147-1-git-send-email-fweisbec@gmail.com> (raw)
In-Reply-To: <20090812100851.GA18577@elte.hu>
On Wed, Aug 12, 2009 at 12:08:51PM +0200, Ingo Molnar wrote:
> yeah. I've zapped those commits from perfcounters/core.
>
> Ingo
Ok, sorry about that.
I've rebuilt a clean tree. It should be fine now.
Thanks.
The following changes since commit 9f8666971185b86615a074bcac67c90fdf8af8bc:
Brice Goglin (1):
perf report: Add raw displaying of per-thread counters
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git \
perfcounters/core
Frederic Weisbecker (3):
perf tools: Factorize high level dso helpers
perf tools: Factorize the event structure definitions in a single file
perf tools: Factorize the map helpers
tools/perf/Makefile | 2 +
tools/perf/builtin-annotate.c | 209 +-------------------------------
tools/perf/builtin-record.c | 20 +---
tools/perf/builtin-report.c | 274 +----------------------------------------
tools/perf/builtin-stat.c | 1 -
tools/perf/builtin-top.c | 24 ----
tools/perf/builtin.h | 1 +
tools/perf/perf.h | 1 +
tools/perf/util/callchain.h | 1 +
tools/perf/util/debug.c | 22 ++++
tools/perf/util/debug.h | 5 +
tools/perf/util/event.h | 84 +++++++++++++
tools/perf/util/map.c | 97 +++++++++++++++
tools/perf/util/symbol.c | 97 +++++++++++++++
tools/perf/util/symbol.h | 12 ++
tools/perf/util/util.h | 1 +
16 files changed, 330 insertions(+), 521 deletions(-)
create mode 100644 tools/perf/util/debug.c
create mode 100644 tools/perf/util/debug.h
create mode 100644 tools/perf/util/event.h
create mode 100644 tools/perf/util/map.c
next prev parent reply other threads:[~2009-08-12 10:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-12 9:25 [GIT PULL] " Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 1/3] perf tools: Factorize high level dso helpers Frederic Weisbecker
2009-08-12 9:59 ` Frederic Weisbecker
2009-08-12 10:08 ` Ingo Molnar
2009-08-12 10:48 ` Frederic Weisbecker [this message]
2009-08-12 10:54 ` [GIT PULL v2] perf tools: Factorize common code Ingo Molnar
2009-08-12 11:00 ` Frederic Weisbecker
2009-08-12 13:54 ` Arnaldo Carvalho de Melo
2009-08-12 14:31 ` Ingo Molnar
2009-08-12 10:48 ` [PATCH 1/3 v2] perf tools: Factorize high level dso helpers Frederic Weisbecker
2009-08-12 10:48 ` [PATCH 2/3 v2] perf tools: Factorize the event structure definitions in a single file Frederic Weisbecker
2009-08-12 10:48 ` [PATCH 3/3 v2] perf tools: Factorize the map helpers Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 2/3] perf tools: Factorize the event structure definitions in a single file Frederic Weisbecker
2009-08-12 9:26 ` [PATCH 3/3] perf tools: Factorize the map helpers Frederic Weisbecker
2009-08-12 9:27 ` [GIT PULL] perf tools: Factorize common code Frederic Weisbecker
2009-08-12 9:32 ` Ingo Molnar
2009-08-12 9:52 ` Peter Zijlstra
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=1250074112-15147-1-git-send-email-fweisbec@gmail.com \
--to=fweisbec@gmail.com \
--cc=Brice.Goglin@inria.fr \
--cc=acme@redhat.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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
all inboxes | Powered by JetHome®