zephyr/tests/benchmarks/object_footprint
Adithya Baglody 22838e8b50 benchmarks: object_footprint: Disable userspace for benchmarks
Disable userspace for benchmarks because it changes the KPI
numbers. It will be re-enabled once the required code is
in place.

Signed-off-by: Adithya Baglody <adithya.nagaraj.baglody@intel.com>
2018-05-31 08:48:07 -04:00
..
src kbuild: Removed KBuild 2017-11-08 20:00:22 -05:00
.gitignore
CMakeLists.txt Introduce cmake-based rewrite of KBuild 2017-11-08 20:00:22 -05:00
Kconfig kconfig: Remove remaining 'option env' bounce symbols 2018-05-28 17:21:11 -04:00
README.txt
prj00.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj01.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj02.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj03.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj04.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj05.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj06.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj07.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj08.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj09.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj10.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
prj11.conf benchmarks: object_footprint: Disable userspace for benchmarks 2018-05-31 08:48:07 -04:00
run.sh tests: use cmake to build object benchmarks 2017-11-08 20:00:22 -05:00
testcase.yaml tests/samples: fixed yaml syntax 2017-12-11 14:47:08 -05:00

README.txt

Title: Object Footprint Measurement

Description:
This sample builds multiple kernels with different configurations
starting with a minimal kernel that basically does nothing and
adds features one by one to measure the minimal footprint for the
various supported kernel objects and features.

Usage:

Execute ./run.sh which will build all configurations and will create
a text file with the footprint results for each configuration.