https://wiki.linaro.org/projects/big.LITTLE.MP
The big.LITTLE MP Project Plan and project documents are currently being updated.
Roadmap Cards ============== Improving HMP Linux scheduling - http://cards.linaro.org/browse/CARD-190
Version 14 of big.LITTLE MP has been pushed. Updates: ------- - Rebased over 3.8-rc2 - per-task-load-average-v3-merged dropped as its already present in 3.8-rc2 - sched-pack-small-tasks-v1-fixed and sched-pack-small-tasks-v1-arm dropped, as sched-pack-small-tasks-v2 contains all required patches. Even sched-pack-small-tasks-v2 is dropped at last moment due to some issues. - Few patches from arm-multi_pmu_v2 dropped as they are already mainlined. - Stats: Total distinct patches: 37 - New Patches: cpufreq-fixes-v2 (5) Details here: http://lists.linaro.org/pipermail/linaro-dev/2013-January/015037.html
Blueprints =========== Big.LITTLE MP blueprints are in the process of being updated to reflect the upcoming development iteration.
https://blueprints.launchpad.net/linaro-android/+spec/cpu-hot-plug-latency https://blueprints.launchpad.net/linaro-power-kernel/+spec/multi-cluster-cpu... https://blueprints.launchpad.net/linaro-power-kernel/+spec/sched-cooperation... https://blueprints.launchpad.net/linaro-power-kernel/+spec/timer-workqueue-c... https://blueprints.launchpad.net/linaro-power-kernel/+spec/power-aware-sched...
Other Efforts ============= The big.LITTLE MP team has just wrapped up a sprint in Cambridge. Items discussed were benchmarking, deliverables, quality assurance, configuration management and how Linaro will accomplish on going support for successive Android kernels. More on these items as they develop.
QA === QA statistics will be available in future updates.
On 25 January 2013 14:04, David Zinman david.zinman@linaro.org wrote:
https://wiki.linaro.org/projects/big.LITTLE.MP
The big.LITTLE MP Project Plan and project documents are currently being updated.
Roadmap Cards
Improving HMP Linux scheduling - http://cards.linaro.org/browse/CARD-190
Version 14 of big.LITTLE MP has been pushed. Updates: ------- - Rebased over 3.8-rc2 - per-task-load-average-v3-merged dropped as its already present in 3.8-rc2 - sched-pack-small-tasks-v1-fixed and sched-pack-small-tasks-v1-arm dropped, as sched-pack-small-tasks-v2 contains all required patches. Even sched-pack-small-tasks-v2 is dropped at last moment due to some issues. - Few patches from arm-multi_pmu_v2 dropped as they are already mainlined. - Stats: Total distinct patches: 37 - New Patches: cpufreq-fixes-v2 (5) Details here: http://lists.linaro.org/pipermail/linaro-dev/2013-January/015037.html
Blueprints
Big.LITTLE MP blueprints are in the process of being updated to reflect the upcoming development iteration.
https://blueprints.launchpad.net/linaro-android/+spec/cpu-hot-plug-latency
https://blueprints.launchpad.net/linaro-power-kernel/+spec/multi-cluster-cpu...
https://blueprints.launchpad.net/linaro-power-kernel/+spec/sched-cooperation...
https://blueprints.launchpad.net/linaro-power-kernel/+spec/timer-workqueue-c...
https://blueprints.launchpad.net/linaro-power-kernel/+spec/power-aware-sched...
Other Efforts
The big.LITTLE MP team has just wrapped up a sprint in Cambridge. Items discussed were benchmarking, deliverables, quality assurance, configuration management and how Linaro will accomplish on going support for successive Android kernels.
Any outcome from this ^^^
We've been discussing this in other contexts and I think it would be good to have a unified plan across Linaro that involves early and often engagement with Google. At this point, as far as I'm aware, Google hasn't picked up the big.LITTLE baton in any significant way.
More on these items as they develop.
QA
QA statistics will be available in future updates.
-- David Zinman, Project Manager Linaro.org | Open source software for ARM SoCs
On Fri, 25 Jan 2013, Zach Pfeffer wrote:
We've been discussing this in other contexts and I think it would be good to have a unified plan across Linaro that involves early and often engagement with Google. At this point, as far as I'm aware, Google hasn't picked up the big.LITTLE baton in any significant way.
The first actors to get involved at this point are silicon vendors as there is hardware specific enablement work.
OTOH our goal is to make big.LITTLE as transparent as possible to user space, so Android should benefit without major changes needed.
Nicolas