From: Michael Ellerman <mpe@ellerman.id.au>
To: Shuah Khan <shuahkh@osg.samsung.com>
Cc: mmarek@suse.cz, gregkh@linuxfoundation.org,
akpm@linux-foundation.org, rostedt@goodmis.org, mingo@redhat.com,
davem@davemloft.net, keescook@chromium.org,
tranmanphong@gmail.com, cov@codeaurora.org,
dh.herrmann@gmail.com, hughd@google.com, bobby.prani@gmail.com,
serge.hallyn@ubuntu.com, ebiederm@xmission.com,
tim.bird@sonymobile.com, josh@joshtriplett.org, koct9i@gmail.com,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v3 00/20] kselftest install target feature
Date: Mon, 29 Dec 2014 15:53:10 +1100 [thread overview]
Message-ID: <1419828790.26911.3.camel@ellerman.id.au> (raw)
In-Reply-To: <cover.1419387513.git.shuahkh@osg.samsung.com>
On Wed, 2014-12-24 at 09:27 -0700, Shuah Khan wrote:
> This patch series adds a new kselftest_install make target
> to enable selftest install. When make kselftest_install is
> run, selftests are installed on the system. A new install
> target is added to selftests Makefile which will install
> targets for the tests that are specified in INSTALL_TARGETS.
> During install, a script is generated to run tests that are
> installed. This script will be installed in the selftest install
> directory. Individual test Makefiles are changed to add to the
> script. This will allow new tests to add install and run test
> commands to the generated kselftest script. kselftest target
> now depends on kselftest_install and runs the generated kselftest
> script to reduce duplicate work and for common look and feel when
> running tests.
>
> This approach leverages and extends the existing framework that
> uses makefile targets to implement run_tests and adds install
> target. This will scale well as new tests get added and makes
> it easier for test writers to add install target at the same
> time new test gets added.
>
> This v3 series reduces duplicate code to generate script
> in indiviual test Makefiles and consolidates support in
> selftests main Makefile. In the main Makefile, it does
> minimal work to set and export install path. In this
> series exec and powerpc tests are not included in the
> install, this work will be done in future patches. exec
> and powerpc are still run when make kselftest is invoked.
Any particular reason you excluded the powerpc tests? Going by a quick count,
powerpc has 32 of the 54 self tests, ie. more than half.
Sorry I didn't get a chance to review v1 or v2, but is this really the best
solution we can come up with? It seems to involve a lot of boiler plate getting
repeated in every Makefile.
I'm off this week so I can't immediately come up with something better, I'll
try in the new year.
cheers
next prev parent reply other threads:[~2014-12-29 5:00 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 16:27 [PATCH v3 00/20] kselftest install target feature Shuah Khan
2014-12-24 16:27 ` [PATCH v3 01/20] selftests/breakpoints: add install target to enable test install Shuah Khan
2014-12-24 16:27 ` [PATCH v3 02/20] selftests/cpu-hotplug: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 03/20] selftests/efivarfs: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 04/20] selftests/firmware: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 05/20] selftests/ftrace: " Shuah Khan
2015-01-02 15:45 ` Steven Rostedt
2015-01-04 5:18 ` Masami Hiramatsu
2015-01-04 5:29 ` Masami Hiramatsu
2015-01-05 18:06 ` Shuah Khan
2014-12-24 16:27 ` [PATCH v3 06/20] selftests/ipc: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 07/20] selftests/kcmp: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 08/20] selftests/memfd: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 09/20] selftests/memory-hotplug: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 10/20] selftests/mount: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 11/20] selftests/mqueue: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 12/20] selftests/net: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 13/20] selftests/ptrace: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 14/20] selftests/size: " Shuah Khan
2015-01-01 2:31 ` WIP alternative - was " Tim Bird
2015-01-05 21:28 ` Shuah Khan
2015-01-05 21:56 ` Tim Bird
2015-01-07 23:22 ` Shuah Khan
2014-12-24 16:27 ` [PATCH v3 15/20] selftests/sysctl: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 16/20] selftests/timers: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 17/20] selftests/user: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 18/20] selftests/vm: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 19/20] selftests: " Shuah Khan
2014-12-24 16:27 ` [PATCH v3 20/20] kbuild: add a new kselftest_install make target to install selftests Shuah Khan
2014-12-29 4:53 ` Michael Ellerman [this message]
2014-12-29 15:24 ` [PATCH v3 00/20] kselftest install target feature Shuah Khan
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=1419828790.26911.3.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=akpm@linux-foundation.org \
--cc=bobby.prani@gmail.com \
--cc=cov@codeaurora.org \
--cc=davem@davemloft.net \
--cc=dh.herrmann@gmail.com \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=hughd@google.com \
--cc=josh@joshtriplett.org \
--cc=keescook@chromium.org \
--cc=koct9i@gmail.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mmarek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=serge.hallyn@ubuntu.com \
--cc=shuahkh@osg.samsung.com \
--cc=tim.bird@sonymobile.com \
--cc=tranmanphong@gmail.com \
/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