Re: [Ksummit-discuss] [CORE TOPIC] stable issues

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

(2014/05/14 5:36), Steven Rostedt wrote:
> On Mon, 12 May 2014 15:55:42 +0900
> Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com> wrote:
> 
> 
>> Agreed. I'd like to suggest adding UT: tag or TS: tag for unit test
>> for testsuite to MAINTAINERS file, which will make clear how to test
>> that subsystem when submitting patches. :)
> 
> That's a good idea.
> 
> I still need to post my ftrace tests somewhere. I could add it to
> tools/testing/selftests, but I break rule #1:
> 
>  *  Do as much as you can if you're not root
> 
> because ftrace only works with root.
> 
> Some of my tests take a bit of time to run as well.

I see. I'd like to have an option to run the test shortly or
full (which takes very long time). For example, probing all kernel
functions with kprobes may take very long time, but I'd like to add
it to kernel tree for stability check. Or should we separate such
time-consuming test from selftest?

> Maybe it's OK to
> just add a tools/testing/tracing directory to place my tests (after
> they get cleaned up to be "public"). Or perhaps just send them to the
> LTP project.

IMHO the tests for debugfs things would better to go into kernel tree,
since their uapi is unstable (not ensured to be stable).

Thank you,

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