Create a plan for testing big.LITTLE

Registered by Paul Larson on 2012-01-27

Initial testing will focus on kernel stability under ubuntu, but eventually android images should be available. Also, we should, at some point expect to have a mechanism for switching manually, and a way to tell which mode the system is running in. Additionally we want to cover some performance testing as well, and there should be instrumentation to help us figure out how long it takes to switch. Useful workloads should be defined for testing.

Blueprint information

Status:
Complete
Approver:
Paul Larson
Priority:
High
Drafter:
Le Chi Thu
Direction:
Approved
Assignee:
Paul Larson
Definition:
Obsolete
Series goal:
None
Implementation:
Beta Available
Milestone target:
milestone icon 2012.03
Started by
Fathi Boudra on 2012-03-08
Completed by
Neil Williams on 2014-07-10

Related branches

Sprints

Whiteboard

[pwlars, 2012-02-23] Moved to 2012.03
[le-chi-thu, 2012-02-24] The draft is done. No further work will be done by me until the big.LITTLE project find out how to continue with the test plan and the resources needed.
[fboudra, 2012-08-03] Chi Thu, please update the work items to reflect what you have done and delivered. Headline/Acceptance should be updated.
[pwlars, 2012-03-08] I basically took over delivery for this recently, so I'll get it cleaned up now

Notes:
Find out more from Usman, regarding items below
Instrumentation
Switching
Performance testing
Stability and robustness testing
Functional testing
CPU stress testing
Itemize switcher use-cases - ie: Under what policy does the
kernel need to switch?

Meta:
Headline: N/A
Acceptance: Signoff and Acceptance of testplan

(?)

Work Items

Work items:
[le-chi-thu] Research big.LITTLE: DONE
[le-chi-thu] Sync with development team on project goals and get recommendations for tests: DONE
[le-chi-thu] Rough draft of test plan: DONE
[le-chi-thu] formalize the testplan into a better template: DONE
Research fast models and how it affects plans for testing big.LITTLE: DONE
Fill in test details: DONE
Create execution plan spreadsheets: DONE
Collect feedback, tweak plan, iterate: INPROGRESS
Get signoff from stakeholders: INPROGRESS

This blueprint contains Public information 
Everyone can see this information.