From: Shuah Khan <shuah.kh@samsung.com>
To: ksummit-discuss@lists.linuxfoundation.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond
Date: Thu, 07 Aug 2014 08:36:05 -0600 [thread overview]
Message-ID: <53E38ED5.9000300@samsung.com> (raw)
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.
What's planned for 3.18 and beyond:
- get feedback on the new kselftest target from the community
- add more tests to be run under kselftest umbrella
- identify existing tests under /lib and other areas that
make a good candidate to be included under kselftest
- Some of these could be run as a tool and/or a independent
test with a few changes and some probably aren't like the
/lib/locking tests.
- As a goal, try to leverage existing tests and modify them
as needed to run them as a black-box test (e.g: look into
ways to make it run as a tool)
- Greg KH sparked the kernel selftest idea, has been in the loop
for the work done so far, and reviewed the plan for 3.18.
thanks,
-- Shuah
Shuah Khan
Senior Linux Kernel Developer - Open Source Group
Samsung Research America(Silicon Valley)
shuah.kh@samsung.com | (970) 672-0658
next reply other threads:[~2014-08-07 14:46 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-07 14:36 Shuah Khan [this message]
2014-08-07 18:24 ` Bird, Tim
2014-08-07 19:59 ` Shuah Khan
2014-08-08 2:18 ` Masami Hiramatsu
2014-08-11 14:11 ` Shuah Khan
2014-08-11 16:13 ` Masami Hiramatsu
2014-08-12 13:00 ` Grant Likely
2014-08-12 16:15 ` Guenter Roeck
2014-08-12 16:21 ` Masami Hiramatsu
2014-08-12 16:51 ` Geert Uytterhoeven
2014-08-12 17:15 ` Theodore Ts'o
2014-08-12 16:23 ` Grant Likely
2014-08-12 16:49 ` Mark Brown
2014-08-13 6:26 ` Grant Likely
2014-08-13 10:40 ` Mark Brown
2014-08-13 11:12 ` Geert Uytterhoeven
2014-08-13 12:42 ` Mark Brown
2014-08-13 13:08 ` Geert Uytterhoeven
2014-08-13 15:00 ` Kevin Hilman
2014-08-13 16:40 ` Olof Johansson
2014-08-13 17:11 ` Mark Brown
2014-08-12 17:46 ` Tim Bird
2014-08-12 18:06 ` Steven Rostedt
2014-08-12 20:52 ` Tim Bird
2014-08-14 16:35 ` Grant Likely
2014-08-12 17:30 ` Andy Lutomirski
2014-08-12 16:34 ` Shuah Khan
2014-08-13 8:35 ` Linus Walleij
2014-08-13 16:11 ` Guenter Roeck
2014-08-13 16:16 ` Andy Lutomirski
2014-08-13 16:44 ` Bird, Tim
2014-08-13 17:07 ` Grant Likely
2014-08-13 17:10 ` Andy Lutomirski
2014-08-13 17:10 ` Guenter Roeck
2014-08-18 3:10 ` Rob Landley
2014-08-18 3:08 ` Rob Landley
2014-08-18 7:16 ` Geert Uytterhoeven
2014-08-13 16:45 ` Masami Hiramatsu
2014-08-18 3:18 ` Rob Landley
2014-08-13 15:06 ` Aneesh Kumar K.V
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=53E38ED5.9000300@samsung.com \
--to=shuah.kh@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
/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