On Wed, Nov 14, 2012 at 06:33:29AM +0000, Viresh Kumar wrote:
Hello everybody,
Hi Viresh,
There have been few discussion on how big LITTLE MP tree should be managed as it is getting PULL requests from a wide range of patches working towards making our system more power efficient.
The following scheme is finalized and is detailed here:
https://wiki.linaro.org/WorkingGroups/PowerManagement/Process/bigLittleMPTre...
Purpose of this tree is to keep all ongoing efforts, which affect power management on big LITTLE systems, together at a single place. All of these must be targeted to get included in Mainline by their original authors.
There are two categories of branches/patches that are kept here. One that are guaranteed to work on current big LITTLE system (Tested on ARM Vexpress TC2)
How is that guarantee created? Do you have a set of tests that you are going to run before declaring it working? Interested to have a bit more detail here.
and others which are experimental. Branches can be moved from experimental to master, once we are convinced they don't break any existing stuff in master branch.
So, following is the category of Merge branches we have:
big-LITTLE-MP-master-v*: Guaranteed to work on current big LITTLE system, ARM Vexpress TC2. This will be pulled in linux-linaro-tracking git tree. big-LITTLE-MP-experimental-v*: Experimental topic branches
For now I have created to merge branches:
- big-LITTLE-MP-master-v12: git merge arm-multi_pmu_v2 hw-bkp-v7.1-debug-v1 per-task-load-average-v3-merged task-placement-v2
task-migration-sysfs-tuning misc-patches config-fragments
- big-LITTLE-MP-exp-v12: git merge intel-powerclamp-driver-v1 per-entity-load-tracking-with-core-sched-v1 sched-pack-small-tasks-v1 sched-timer-wq-migration-v2-resend
Not exactly clear what is the transition process from experimental to master.
And another question: is there going to be an implicit order in pulling patches in your master branch? (i.e. you pull first the old patches that are known to work because they were previously in -master- before pulling patches from -experimental- ? )
Regards, Liviu
- power-aware-scheduling-v1: This is another branch which is present
in this tree, which can be used. It was rebased on tip/master and hence isn't merged.
PULL request to Andrey would be sent only for the Master branch. I would be releasing Experimental branch too every time with Master branch though.
Please share your comments?
-- viresh