Re: Re: [RFC][PATCH] ftracetest: Add a couple of ftrace test cases

[Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>]

(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@osg.samsung.com> 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
>>> thread:
>>>
>>> https://lkml.org/lkml/2014/9/23/926
>>>
>>
>> Thanks,
>>
>> 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.

Anyway, at first we'd better add simpler tests which is not relay on
other tools except busybox shell.

Thank you,


-- 
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Research Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com