linux-kernel - RFC: kselftest size roadmap

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 4 Dec 2014 08:56:29 -0800
From:	Tim Bird <tim.bird@...ymobile.com>
To:	Josh Triplett <josh@...htriplett.org>
CC:	Shuah Khan <shuahkh@....samsung.com>,
	"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@...e-electrons.com>,
	Michael Ellerman <mpe@...erman.id.au>,
	"linux-embedded@...r.kernel.org" <linux-embedded@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RFC: kselftest size roadmap

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/