Re: Re: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases
From: Masami Hiramatsu
Date: Mon Sep 29 2014 - 07:41:03 EST
(2014/09/26 23:46), Namhyung Kim wrote:
> Hi Masami,
> 2014-09-26 (ê), 20:54 +0900, Masami Hiramatsu:
>> (2014/09/26 15:06), Namhyung Kim wrote:
>>> Hi Steve,
>>> On Wed, 24 Sep 2014 12:08:53 -0400, Steven Rostedt wrote:
>>>> On Wed, 24 Sep 2014 10:01:38 -0600
>>>> Shuah Khan <shuahkh@xxxxxxxxxxxxxxx> wrote:
>>>>> I am working on adding the framework for c tests. We will have
>>>>> to get this evolved for shell scripts. Please see the following
>>>> Also, what's the rules for a test that requires other tools. Some of my
>>>> tests require trace-cmd to be installed as well as perf. My stress test
>>>> runs perf against trace-cmd running hackbench (another required tool),
>>>> but I believe that perf has hackbench built in so I could replace
>>>> hackbench with the perf version.
>>> Yeah, and I think we can at least build perf (if not found) for test as
>>> we can always have the source. The trace-cmd is different and it'd be
>>> another reason I need to work on 'perf ftrace' command soon. ;-)
>> +1 :)
>> For the kselftest, we can only expect to have tools in kernel tree (which
>> should be static-linked) and busybox, so that we can use qemu emulator to
>> run kselftest on other archs. I guess perf still need some shared
>> objects to run. That should be solved too.
> 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.
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/