From: Namhyung Kim <namhyung@kernel.org>
To: David Ahern <dsahern@gmail.com>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@kernel.org>,
LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>
Subject: Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2)
Date: Mon, 25 Jun 2012 09:51:00 +0900 [thread overview]
Message-ID: <87sjdkuscr.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <4FE49C2D.3000509@gmail.com> (David Ahern's message of "Fri, 22 Jun 2012 10:24:13 -0600")
Hi, David
On Fri, 22 Jun 2012 10:24:13 -0600, David Ahern wrote:
> On 6/22/12 10:14 AM, Arnaldo Carvalho de Melo wrote:
>> I think at least the .dymsym symbol table is present in DSOs, aka
>> libraries, otherwise how will they dynamicly link?
>>
> yes. I meant debug information wise - everything is stripped during
> packaging phase, so onbox analysis is severely limited in address to
> symbol resolutions.
>
Right, I was saying about a case of the onbox recording and off-line
analysis - I hope I didn't use vague words here. And I thought that
supporting build-id is helpful (not crucial, though) for the case too.
Thanks,
Namhyung
next prev parent reply other threads:[~2012-06-25 0:54 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 ` [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2) Peter Zijlstra
2012-06-22 15:05 ` 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 [this message]
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=87sjdkuscr.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=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=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