From: Tim Bird <tim.bird@sonymobile.com>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Shuah Khan <shuahkh@osg.samsung.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Michael Ellerman <mpe@ellerman.id.au>,
"linux-embedded@vger.kernel.org" <linux-embedded@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RFC: kselftest size roadmap
Date: Thu, 4 Dec 2014 08:56:29 -0800 [thread overview]
Message-ID: <5480923D.5010503@sonymobile.com> (raw)
In-Reply-To: <20141204003653.GA5004@thin>
Here's an RFC on my roadmap for the kselftest size test going forward...
In the long term, I'd like to be able to use the test for bisecting
size regressions, and to allow any kernel developer to use this even if they
don't have hardware for a particular architecture.
What I'd like to add to this in the future:
- cleaned up approach to cross-compilation
- put CROSS_COMPILE handling outside sub-directory Makefiles
- this should include support for KBUILD_OUTPUT
- handle CFLAGS for user-space programs (as opposed to
kernel CFLAGS), and in a unified way
- ability to run on target or in emulator
- will involve adding an "install phase", and
possibly a "collect results" phase. These are needed
throughout kselftest to do any host/target
testing.
- add a size threshold parameter to allow the
test to check for a regression
- test needs to return failure code that git
bisect can use (not sure about mechanism for this yet)
- regression test might utilize a feature to save off a
"baseline" size to measure against, for the ability
to indicate a regression as "current size > baseline + 20k"
Any feedback on this?
Thanks,
-- Tim
prev parent reply other threads:[~2014-12-04 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-03 18:42 [PATCH v6] selftest: size: Add size test for Linux kernel Tim Bird
[not found] ` <547F598D.7030205-/MT0OVThwyLZJqsBc5GL+g@public.gmane.org>
2014-12-04 0:36 ` Josh Triplett
2014-12-04 0:50 ` Shuah Khan
[not found] ` <547FAFC3.40609-JPH+aEBZ4P+UEJcrhfAQsw@public.gmane.org>
2014-12-04 2:33 ` Shuah Khan
2014-12-04 16:56 ` Tim Bird [this message]
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=5480923D.5010503@sonymobile.com \
--to=tim.bird@sonymobile.com \
--cc=josh@joshtriplett.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpe@ellerman.id.au \
--cc=shuahkh@osg.samsung.com \
--cc=thomas.petazzoni@free-electrons.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;
as well as URLs for NNTP newsgroup(s).