prepare IKS testing code to detect cpu topology
Current big.LITTLE IKS test suite is designed to run on TC2 and RTSM platform. But members will be having different platforms with different number of CPUs and its topology. Test suite need to be modified to detect CPU topology at run time.
Blueprint information
- Status:
- Complete
- Approver:
- Milosz Wasilewski
- Priority:
- High
- Drafter:
- Naresh Kamboju
- Direction:
- Needs approval
- Assignee:
- Naresh Kamboju
- Definition:
- New
- Series goal:
- None
- Implementation:
-
Implemented
- Milestone target:
-
2013.05
- Started by
- Naresh Kamboju
- Completed by
- Naresh Kamboju
Related branches
Related bugs
| Bug #1170689: cpu-freq-vs-cluster-freq failed when TC2 boots on A7 | Fix Released |
| Bug #1172129: Workload automation: Need a generic library in the test suite that detects cpu topology | Invalid |
Sprints
Whiteboard
[nkambo May 8 2013] Started working on getting fast cpu and slow cpu numbers.
[nkambo May 10 2013] new utility tool "affinity_tools" is added to bL IKS test suite. Added get_no_of_cpus funcation in the test scripts which detects no of cpus at run time.
Discussion regarding using /proc/cpuinfo to detect cpu numbers.
<nkambo> npitre, regarding the detecting fast and slow cpus.... at run time
<nkambo> npitre, https:/
<npitre> nkambo: and your question is ?
<nkambo> npitre, I am happy to read data from /proc/cpuinfo and grep CPU part
<nkambo> npitre, you were suggestion to read this kind of data from /proc/device-tree
<nkambo> npitre, is that correct ?
<nkambo> npitre, is there any flaw if i read it from /proc/cpuinfo ?
<npitre> nkambo: it is valid only when the switcher is disabled
<nkambo> npitre, perfect
<npitre> nkambo: when the switcher is enabled, sometimes CPU0 may be an A7, sometimes it may be an A15
<nkambo> npitre, if the switcher is enable...we do not need to know which is fast and slow
<npitre> nkambo: and right now the /proc/cpuinfo information is not updated when a switch occurs
<nkambo> npitre, in IKS .... i need to detect only number of cpus ...not the fast and slow... but in case of MP tests ... i need to know fast and slow cpus
<nkambo> npitre, like in case of workload automation and scheduler tests
<nkambo> npitre, not in case of BL IKS core test suite.
<npitre> nkambo: in that case thats fine
<nkambo> npitre, cool .. thanks
[nkambo May 20 2013]
ACTION: Naresh to get help from Chander (Samsung) to get it tested on Samsung’s b.L platform
Waiting for Chander’s test report generated on samsung hardware.
[nkambo May 22 2013]
Chander do not have any working hardware for this as of now. As far as
adonis is concerned they have been taken back to HQ.
[nkambo May 23 2013]
Testing is completed on TC2 and results reported as been shared as a part of weekly testing.
Testing on adonis is not done due to unavailability of hardware. This action has been moved to next cycle https:/
Meta:
Roadmap id: big.LITTLE Project
Headline: Prepare big.LITTLE IKS test code to detect cpu topology
Acceptance: big.LITTLE IKS should run on any kind of IKS enabled platform.
Deliverables: big.LITTLE IKS test suite.
Work Items
Work items:
create a mechanism to detect cpu topology in test suite: DONE
Test suite should able to run on any kind of platform and any kind of CPU topology : POSTPONED
