Benchmark EEMBC, denbench and coremark

Registered by Andy Doan on 2012-03-06

We need to add the ability to internally run some of the same restricted benchmark the toolchain team does, but on Android. The code/binaries/results for these benchmarks can't be shared externally.

The idea for this is to create the required benchmark files/binaries in private builds. We'll put these files behind a password protected HTTP directory. We'll then have lava-android-test modules written for each benchmark. These modules will have the logic to download the code they need onto the Android device and then run the benchmark.

Blueprint information

Status:
Complete
Approver:
Zach Pfeffer
Priority:
High
Drafter:
Andy Doan
Direction:
Approved
Assignee:
Andy Doan
Definition:
Approved
Series goal:
Accepted for 2012q1
Implementation:
Implemented
Milestone target:
milestone icon 12.03
Started by
Zach Pfeffer on 2012-03-06
Completed by
Zach Pfeffer on 2012-03-27

Related branches

Sprints

Whiteboard

Notes:
[2012/3/6 pfefferz] Put notes here.
[2012/3/14 doanac] LAVA is not yet ready for private bundles and such, so for now I'm just going to run own private LAVA tests (nothing commited to mainline) for these benchmarks.
[2012/3/14 doanac] We have eembc, coremark, and denbench. I think spec2k is a lot of work. Is it worth doing it right now?
[2012/3/27] Spec2000 work removed due to usefulness consideration

Meta:
Roadmap id: ANDROID2012-Q1-TOOLCHAIN
Headline: EEMBC, denbench and coremark have been run on Linaro's Android baseline
Acceptance: EEMBC, denbench and coremark are run on each android-build.

(?)

Work Items

Work items:
Build coremark for Android: DONE
Create lava-android-test for coremark: DONE
Build denbench for Android: DONE
Create lava-android-test for denbench: DONE
Build EEMBC for Android: DONE
Create lava-android-test for EEMBC: DONE

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.