From: Namhyung Kim <namhyung.kim@lge.com>
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@redhat.com>,
LKML <linux-kernel@vger.kernel.org>,
Stephane Eranian <eranian@google.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [RFC 0/5] perf tools: Minimalistic build without libelf dependency
Date: Tue, 22 May 2012 09:20:42 +0900 [thread overview]
Message-ID: <87aa112hid.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <4FBA5937.2050701@gmail.com> (David Ahern's message of "Mon, 21 May 2012 09:03:19 -0600")
Hi, David
On Mon, 21 May 2012 09:03:19 -0600, David Ahern wrote:
> One idea that has been proposed is to make perf configurable - to pick
> and choose which pieces you want built-in. For example for target
> systems only compile in record command. It seems like that part should
> be done first and would potentially handle a lot of these changes.
>
Yeah, I remember Arnaldo said about the menuconfig-like configuration
interface. But I'd like to finish this minimal build patchset first
since the configuration change can require much work on where I'm not
familiar with and I doubt the users care about it much.
Anyway, thanks for the comment.
Namhyung
prev parent reply other threads:[~2012-05-22 0:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 7:10 Namhyung Kim
2012-05-14 7:10 ` [PATCH 1/5] perf symbols: Introduce symbol__elf_init() Namhyung Kim
2012-05-14 7:10 ` [PATCH 2/5] perf symbols: Do not use ELF's symbol binding constants Namhyung Kim
2012-05-14 7:10 ` [PATCH 3/5] perf tools: Split out util/symbol-elf.c Namhyung Kim
2012-05-21 11:45 ` Jiri Olsa
2012-05-22 1:00 ` Namhyung Kim
2012-05-22 8:35 ` Jiri Olsa
2012-05-14 7:10 ` [PATCH 4/5] perf tools: Support minimal build Namhyung Kim
2012-05-14 7:10 ` [PATCH 5/5] perf symbols: Implement poor man's ELF parser Namhyung Kim
2012-05-21 11:47 ` Jiri Olsa
2012-05-22 1:08 ` Namhyung Kim
2012-05-22 7:52 ` Peter Zijlstra
2012-05-22 10:26 ` Namhyung Kim
2012-05-22 10:44 ` Peter Zijlstra
2012-05-14 9:22 ` [RFC 0/5] perf tools: Minimalistic build without libelf dependency Ingo Molnar
2012-05-15 0:40 ` Namhyung Kim
2012-05-21 6:00 ` Namhyung Kim
2012-05-21 15:03 ` David Ahern
2012-05-22 0:20 ` Namhyung Kim [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=87aa112hid.fsf@sejong.aot.lge.com \
--to=namhyung.kim@lge.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
Powered by JetHome