From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
David Ahern <dsahern@gmail.com>
Subject: Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2)
Date: Fri, 22 Jun 2012 11:47:58 +0200 [thread overview]
Message-ID: <1340358478.18025.51.camel@twins> (raw)
In-Reply-To: <1340343462-15556-1-git-send-email-namhyung@kernel.org>
On Fri, 2012-06-22 at 14:37 +0900, Namhyung Kim wrote:
> And then I realized that the perf record needs to know about the
> build-id's anyway. :( So I implemented a poor man's version of elf
> parser only for parsing the build-id info.
Why? the very first versions didn't know about any of that nonsense :-)
It works just fine as long as you don't go change binaries around.
That said, you did the work already, so no objection, just saying
builtids aren't that important.
next prev parent reply other threads:[~2012-06-22 9:48 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 5:37 [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2) Namhyung Kim
2012-06-22 5:37 ` [PATCH 1/8] perf evsel: Fix a build failure on cross compilation Namhyung Kim
2012-06-22 5:37 ` [PATCH 2/8] tools lib traceevent: Make dependency files regeneratable Namhyung Kim
2012-06-28 16:15 ` Arnaldo Carvalho de Melo
2012-07-06 10:52 ` [tip:perf/core] " tip-bot for Namhyung Kim
2012-06-22 5:37 ` [PATCH 3/8] tools lib traceevent: Detect build environment changes Namhyung Kim
2012-06-22 5:37 ` [PATCH 4/8] perf symbols: Introduce symbol__elf_init() Namhyung Kim
2012-06-22 5:37 ` [PATCH 5/8] perf symbols: Do not use ELF's symbol binding constants Namhyung Kim
2012-06-22 12:43 ` Arnaldo Carvalho de Melo
2012-06-22 15:19 ` Namhyung Kim
2012-06-22 15:29 ` Arnaldo Carvalho de Melo
2012-06-22 5:37 ` [PATCH 6/8] perf tools: Split out util/symbol-elf.c Namhyung Kim
2012-06-22 5:37 ` [PATCH 7/8] perf tools: Support minimal build without libelf Namhyung Kim
2012-06-22 5:37 ` [PATCH 8/8] perf symbols: Implement poor man's ELF parser Namhyung Kim
2012-06-22 9:47 ` Peter Zijlstra [this message]
2012-06-22 15:05 ` [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2) Namhyung Kim
2012-06-22 15:18 ` David Ahern
2012-06-22 15:30 ` Namhyung Kim
2012-06-22 15:35 ` David Ahern
2012-06-22 16:14 ` Arnaldo Carvalho de Melo
2012-06-22 16:24 ` David Ahern
2012-06-25 0:51 ` Namhyung Kim
2012-06-22 15:32 ` Arnaldo Carvalho de Melo
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=1340358478.18025.51.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=paulus@samba.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