mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Namhyung Kim <namhyung@kernel.org>
To: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
	Shuah Khan <shuahkh@osg.samsung.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Shuah Khan <shuah.kh@samsung.com>,
	Tom Zanussi <tom.zanussi@linux.intel.com>,
	Oleg Nesterov <oleg@redhat.com>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases
Date: Tue, 30 Sep 2014 15:24:01 +0900	[thread overview]
Message-ID: <87r3ythbi6.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <54294543.2030003@hitachi.com> (Masami Hiramatsu's message of "Mon, 29 Sep 2014 20:40:51 +0900")

Hi Masami,

On Mon, 29 Sep 2014 20:40:51 +0900, Masami Hiramatsu wrote:
> (2014/09/26 23:46), Namhyung Kim wrote:
>> The perf should be built with no extra dependencies (other than libc).
>> It won't provide rich features but basic functionality (record, report,
>> stat) should be supported.  And I'm also thinking about implementing a
>> very simple elf parser for symbol loading in such a minimal build.
>
> Maybe you can install some static libraries (e.g. elfutils-libelf-devel-static
> on fedora) for enabling it. :)
> Some libraries may not work, but I could enable libelf by installing that.

Yep, installing static libs should also work.  But I'd like to have
minimal depencency especially for embedded systems.  And AFAIK cross
building elfutils/libelf always has been a PITA.

Thanks,
Namhyung

  reply	other threads:[~2014-09-30  6:24 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-23 21:38 Steven Rostedt
2014-09-24  2:58 ` Masami Hiramatsu
2014-09-24 15:42   ` Steven Rostedt
2014-09-24 15:58     ` Steven Rostedt
2014-09-24 16:01       ` Shuah Khan
2014-09-24 16:08         ` Steven Rostedt
2014-09-24 16:22           ` Shuah Khan
2014-09-24 16:30             ` Steven Rostedt
2014-09-24 16:36               ` Shuah Khan
2014-09-26 12:04                 ` Masami Hiramatsu
2014-09-26 14:18                   ` Steven Rostedt
2014-09-29 10:33                     ` Masami Hiramatsu
2014-09-26  6:06           ` Namhyung Kim
2014-09-26 11:54             ` Masami Hiramatsu
2014-09-26 14:46               ` Namhyung Kim
2014-09-29 11:40                 ` Masami Hiramatsu
2014-09-30  6:24                   ` Namhyung Kim [this message]
2014-09-26 14:07             ` Steven Rostedt
2014-09-25  0:35       ` Masami Hiramatsu
2014-09-25  1:14         ` Steven Rostedt
2014-09-25  3:20           ` Masami Hiramatsu
2014-09-25  1:29     ` Masami Hiramatsu

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=87r3ythbi6.fsf@sejong.aot.lge.com \
    --to=namhyung@kernel.org \
    --cc=fengguang.wu@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=shuah.kh@samsung.com \
    --cc=shuahkh@osg.samsung.com \
    --cc=tom.zanussi@linux.intel.com \
    /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