Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond

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

(2014/08/11 23:11), Shuah Khan wrote:
>> (2014/08/07 23:36), Shuah Khan wrote:> As a first step towards a larger goal to enable developer
>>> friendly kernel testing framework, a new make target is
>>> planned for 3.17. In addition, 3.17 includes work done to
>>> fix tools/testing/sefltests to run without failures.
>>>
>>> Short summary of work done so far for 3.17:
>>>
>>> - fix compile errors and warnings in various tests
>>> - fix run-time errors when tests aren't run as root
>>> - enhance and improve cpu and memory hot-plug tests
>>>     to run in limited scope mode by default. A new make
>>>     target to select full-scope testing. Prior to this
>>>     change, cpu and memory hot-plug tests hung trying to
>>>     hot-plug all but cpu0 and a large portion of the memory.
>>> - add a new kselftest target to run existing selftests
>>>     to start with.
>>
>> Instead of running the selftests, can we build the testcases and
>> install it as a tool? I think running tests on the tree is not a
>> good idea...
> 
> One of the goals is to leverage developer tests that we already have.
> When a developer makes a kernel change and wants to see if that change
> lead to any regression, having the ability to buidl and run selftests on 
> the newly installed kernel withe the same source tree is very useful.
> That is the reason behind adding this new target.

I see, for that purpose, installing testcase may not fit.
BTW, how would it cover cross-build?

> Existing selfests are a collection of tools that exercise several
> testcases that are specific each area they target. This is a good
> start and we can definitely start enhancing the tools and build
> testcases.

Agreed.

> 
>> Also, as I said in above mail, I'd like to suggest to add at least
>> log management and statistics to the test. Those are good to automate
>> regression tests. :)
>>
> 
> Right. Some existing selftests do that, but not all. It would be
> helpful to add that to all.

Yeah, and I hope the selftest top-level script to provide such
functions to each test, because those should be common, and easy
to manage.

Thank you,

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