From: David Ahern <dsahern@gmail.com>
To: Namhyung Kim <namhyung@gmail.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
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>
Subject: Re: [RFC/PATCHSET 0/8] perf tools: Minimal build without libelf dependency (v2)
Date: Fri, 22 Jun 2012 09:35:37 -0600 [thread overview]
Message-ID: <4FE490C9.1020903@gmail.com> (raw)
In-Reply-To: <1340379000.1478.34.camel@leonhard>
On 6/22/12 9:30 AM, Namhyung Kim wrote:
>> And build-id's are not required for report (-B option for record).
>>
>> Also, the intent is for a small footprint binary for embedded systems.
>> On such a system I would expect binaries and libraries to be stripped,
>> so no point in running perf-archive.
>>
>
> But is there a chance that binaries on host still contains symbol (and
> debug) information even for those cases?
>
AFAIK embedded systems do not have the luxury of symbols; the goal is as
small as possible. All debugging information is left on the build
servers for off line analysis. That's certainly true for the product I
work on.
David
next prev parent reply other threads:[~2012-06-22 15:35 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 [this message]
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=4FE490C9.1020903@gmail.com \
--to=dsahern@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--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