{"push_id":2794435291,"size":10,"distinct_size":10,"ref":"refs/heads/eas-wip-4","head":"0842e4e342ecdf014c00b6b9785c527bed77b223","before":"6ddccddb901f21de3e66eeed4b14bf6fb1685f06","commits":[{"sha":"df7a45935e23232a26262d5459ad316fd8219a9f","author":{"name":"Srinath Sridharan","email":"809229952ed61526ba428cdd26e616a82cce1de1@google.com"},"message":"eas/sched/fair: Fixing comments in find_best_target.\n\nChange-Id: I83f5b9887e98f9fdb81318cde45408e7ebfc4b13\nSigned-off-by: Srinath Sridharan <srinathsr@google.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/df7a45935e23232a26262d5459ad316fd8219a9f"},{"sha":"31ed56e04ca3b52ff76c1378897ce9ab82ece708","author":{"name":"Chris Redpath","email":"ae54b883c23fde04daba73ac75796ae299bcb360@arm.com"},"message":"sched/walt: Drop arch-specific timer access\n\nOn at least one platform, occasionally the timer providing the wallclock\nwas able to be reset/go backwards for at least some time after wakeup.\n\nAccept that this might happen and warn the first time, but otherwise just\ncarry on.\n\nChange-Id: Id3164477ba79049561af7f0889cbeebc199ead4e\nSigned-off-by: Chris Redpath <chris.redpath@arm.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/31ed56e04ca3b52ff76c1378897ce9ab82ece708"},{"sha":"c937ef6ace4f5410c4a9a07597c90b92a9f9850f","author":{"name":"Caesar Wang","email":"6a97ab1d8fae3a62719c8e695586fe709398a94a@rock-chips.com"},"message":"sched/fair: remove printk while schedule is in progress\n\nIt will cause deadlock and while(1) if call printk while schedule is in\nprogress. The block state like as below:\n\ncpu0(hold the console sem):\nprintk->console_unlock->up_sem->spin_lock(&sem->lock)->wake_up_process(cpu1)\n->try_to_wake_up(cpu1)->while(p->on_cpu).\n\ncpu1(request console sem):\nconsole_lock->down_sem->schedule->idle_banlance->update_cpu_capacity->\nprintk->console_trylock->spin_lock(&sem->lock).\n\np->on_cpu will be 1 forever, because the task is still running on cpu1,\nso cpu0 is blocked in while(p->on_cpu), but cpu1 could not get\nspin_lock(&sem->lock), it is blocked too, it means the task will running\non cpu1 forever.\n\nSigned-off-by: Caesar Wang <wxt@rock-chips.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/c937ef6ace4f5410c4a9a07597c90b92a9f9850f"},{"sha":"0c6e3fa3c1d8f98466c9827bdfe88ac2703d64d1","author":{"name":"John Stultz","email":"33837adfb53316eae44aad04041e1240088d76fd@linaro.org"},"message":"sched: Add Kconfig option DEFAULT_USE_ENERGY_AWARE to set ENERGY_AWARE feature flag\n\nThe ENERGY_AWARE sched feature flag cannot be set unless\nCONFIG_SCHED_DEBUG is enabled.\n\nSo this patch allows the flag to default to true at build time\nif the config is set.\n\nChange-Id: I8835a571fdb7a8f8ee6a54af1e11a69f3b5ce8e6\nSigned-off-by: John Stultz <john.stultz@linaro.org>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/0c6e3fa3c1d8f98466c9827bdfe88ac2703d64d1"},{"sha":"a53f967ece14e2652d25486d4988dde0b6a58c62","author":{"name":"Amit Pundir","email":"a4a7d486fe874593b021ebde938f459c081be043@linaro.org"},"message":"ANDROID: sched/tune: Remove leftover instances of allow_attach\n\nSigned-off-by: Amit Pundir <amit.pundir@linaro.org>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/a53f967ece14e2652d25486d4988dde0b6a58c62"},{"sha":"ab961c90b5fae6394c5dfeef3ed4e7eb685b7b58","author":{"name":"Viresh Kumar","email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org"},"message":"cpufreq: sched: Fix kernel crash on accessing sysfs file\n\nIf the cpufreq driver hasn't set the CPUFREQ_HAVE_GOVERNOR_PER_POLICY\nflag, then the kernel will crash on accessing sysfs files for the sched\ngovernor.\n\nCPUFreq governors we can have the governor specific sysfs files in two\nplaces:\n\nA. /sys/devices/system/cpu/cpuX/cpufreq/<governor>\nB. /sys/devices/system/cpu/cpufreq/<governor>\n\nThe case A. is for governor per policy case, where we can control the\ngovernor tunables for each policy separately. The case B. is for system\nwide tunable values.\n\nThe schedfreq governor only implements the case A. and not B.  The sysfs\nfiles in case B will still be present in\n/sys/devices/system/cpu/cpufreq/<governor>, but accessing them will\ncrash kernel as the governor doesn't support that.\n\nMoreover the sched governor is pretty new and will be used only for the\nARM platforms and there is no need to support the case B at all.\n\nHence use policy->kobj instead of get_governor_parent_kobj(), so that we\nalways create the sysfs files in path A.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/ab961c90b5fae6394c5dfeef3ed4e7eb685b7b58"},{"sha":"c3dc07c6cf747f0120857a15adc9c104c457bab6","author":{"name":"Ke Wang","email":"076764b2b3ebcd2db33ce73678a7b4d1b9f19087@spreadtrum.com"},"message":"sched: tune: Fix lacking spinlock initialization\n\nThe spinlock used by boost_groups in sched tune must be initialized.\nThis commit fixes this lack and the following errors:\n\n[    0.384739] c2 BUG: spinlock bad magic on CPU#2, swapper/2/0\n[    0.390313] c2  lock: 0xffffffc15fe1fc80, .magic:00000000, .owner: <none>/-1, .owner_cpu: 0\n[    0.398739] c2 CPU: 2 PID: 0 Comm: swapper/2 Not tainted 4.4.6+ #4\n[    0.404816] c2 Hardware name: Spreadtrum SP9860gBoard (DT)\n[    0.410462] c2 Call trace:\n[    0.413159] c2 [<ffffff800808b50c>] dump_backtrace+0x0/0x210\n[    0.418803] c2 [<ffffff800808b73c>] show_stack+0x20/0x28\n[    0.424100] c2 [<ffffff8008433310>] dump_stack+0xa8/0xe0\n[    0.429398] c2 [<ffffff8008139398>] spin_dump+0x78/0x9c\n[    0.434608] c2 [<ffffff80081393ec>] spin_bug+0x30/0x3c\n[    0.439644] c2 [<ffffff80081394e4>] do_raw_spin_lock+0xac/0x1b4\n[    0.445639] c2 [<ffffff8008abffe4>] _raw_spin_lock_irqsave+0x58/0x68\n[    0.451977] c2 [<ffffff800812a560>] schedtune_enqueue_task+0x84/0x3bc\n[    0.458320] c2 [<ffffff8008111678>] enqueue_task_fair+0x438/0x208c\n[    0.464487] c2 [<ffffff80080feeec>] activate_task+0x70/0xd0\n[    0.470130] c2 [<ffffff80080ff4a4>] ttwu_do_activate.constprop.131+0x4c/0x98\n[    0.477079] c2 [<ffffff80081005d0>] try_to_wake_up+0x254/0x54c\n[    0.482899] c2 [<ffffff80081009d4>] default_wake_function+0x30/0x3c\n[    0.489154] c2 [<ffffff8008122464>] autoremove_wake_function+0x3c/0x6c\n[    0.495754] c2 [<ffffff8008121b70>] __wake_up_common+0x64/0xa4\n[    0.501574] c2 [<ffffff8008121e9c>] __wake_up+0x48/0x60\n[    0.506788] c2 [<ffffff8008150fac>] rcu_gp_kthread_wake+0x50/0x5c\n[    0.512866] c2 [<ffffff8008151fec>] note_gp_changes+0xac/0xd4\n[    0.518597] c2 [<ffffff8008153044>] rcu_process_callbacks+0xe8/0x93c\n[    0.524940] c2 [<ffffff80080d0b84>] __do_softirq+0x24c/0x5b8\n[    0.530584] c2 [<ffffff80080d1284>] irq_exit+0xc0/0xec\n[    0.535623] c2 [<ffffff8008144208>] __handle_domain_irq+0x94/0xf8\n[    0.541789] c2 [<ffffff8008082554>] gic_handle_irq+0x64/0xc0\n\nSigned-off-by: Ke Wang <ke.wang@spreadtrum.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/c3dc07c6cf747f0120857a15adc9c104c457bab6"},{"sha":"3fdaf94d6250a82bcabe71bc9b4661a7ed1357c5","author":{"name":"Juri Lelli","email":"bdc6bcd4e8b34b4b92413d758024aeca6da0e459@arm.com"},"message":"sched/walt: kill {min,max}_capacity\n\n{min,max}_capacity are static variables that are only updated from\n__update_min_max_capacity(), but not used anywhere else.\n\nRemove them together with the function updating them. This has also\nthe nice side effect of fixing a LOCKDEP warning related to locking\nall CPUs in update_min_max_capacity(), as reported by Ke Wang:\n\n[    2.853595] c0 =============================================\n[    2.859219] c0 [ INFO: possible recursive locking detected ]\n[    2.864852] c0 4.4.6+ #5 Tainted: G        W\n[    2.869604] c0 ---------------------------------------------\n[    2.875230] c0 swapper/0/1 is trying to acquire lock:\n[    2.880248]  (&rq->lock){-.-.-.}, at: [<ffffff80081241cc>] cpufreq_notifier_policy+0x2e8/0x37c\n[    2.888815] c0\n[    2.888815] c0 but task is already holding lock:\n[    2.895132]  (&rq->lock){-.-.-.}, at: [<ffffff80081241cc>] cpufreq_notifier_policy+0x2e8/0x37c\n[    2.903700] c0\n[    2.903700] c0 other info that might help us debug this:\n[    2.910710] c0  Possible unsafe locking scenario:\n[    2.910710] c0\n[    2.917112] c0        CPU0\n[    2.919795] c0        ----\n[    2.922478]   lock(&rq->lock);\n[    2.925507]   lock(&rq->lock);\n[    2.928536] c0\n[    2.928536] c0  *** DEADLOCK ***\n[    2.928536] c0\n[    2.935200] c0  May be due to missing lock nesting notation\n[    2.935200] c0\n[    2.942471] c0 7 locks held by swapper/0/1:\n[    2.946623]  #0:  (&dev->mutex){......}, at: [<ffffff800850e118>] __driver_attach+0x64/0xb8\n[    2.954931]  #1:  (&dev->mutex){......}, at: [<ffffff800850e128>] __driver_attach+0x74/0xb8\n[    2.963239]  #2:  (cpu_hotplug.lock){++++++}, at: [<ffffff80080cb218>] get_online_cpus+0x48/0xa8\n[    2.971979]  #3:  (subsys mutex#6){+.+.+.}, at: [<ffffff800850bed4>] subsys_interface_register+0x44/0xc0\n[    2.981411]  #4:  (&policy->rwsem){+.+.+.}, at: [<ffffff8008720338>] cpufreq_online+0x330/0x76c\n[    2.990065]  #5:  ((cpufreq_policy_notifier_list).rwsem){.+.+..}, at: [<ffffff80080f3418>] blocking_notifier_call_chain+0x38/0xc4\n[    3.001661]  #6:  (&rq->lock){-.-.-.}, at: [<ffffff80081241cc>] cpufreq_notifier_policy+0x2e8/0x37c\n[    3.010661] c0\n[    3.010661] c0 stack backtrace:\n[    3.015514] c0 CPU: 0 PID: 1 Comm: swapper/0 Tainted: G        W 4.4.6+ #5\n[    3.022864] c0 Hardware name: Spreadtrum SP9860g Board (DT)\n[    3.028402] c0 Call trace:\n[    3.031092] c0 [<ffffff800808b50c>] dump_backtrace+0x0/0x210\n[    3.036716] c0 [<ffffff800808b73c>] show_stack+0x20/0x28\n[    3.041994] c0 [<ffffff8008433310>] dump_stack+0xa8/0xe0\n[    3.047273] c0 [<ffffff80081349e0>] __lock_acquire+0x1e0c/0x2218\n[    3.053243] c0 [<ffffff80081353c0>] lock_acquire+0xe0/0x280\n[    3.058784] c0 [<ffffff8008abfdfc>] _raw_spin_lock+0x44/0x58\n[    3.064407] c0 [<ffffff80081241cc>] cpufreq_notifier_policy+0x2e8/0x37c\n[    3.070983] c0 [<ffffff80080f3458>] blocking_notifier_call_chain+0x78/0xc4\n[    3.077820] c0 [<ffffff8008720294>] cpufreq_online+0x28c/0x76c\n[    3.083618] c0 [<ffffff80087208a4>] cpufreq_add_dev+0x98/0xdc\n[    3.089331] c0 [<ffffff800850bf14>] subsys_interface_register+0x84/0xc0\n[    3.095907] c0 [<ffffff800871fa0c>] cpufreq_register_driver+0x168/0x28c\n[    3.102486] c0 [<ffffff80087272f8>] sprd_cpufreq_probe+0x134/0x19c\n[    3.108629] c0 [<ffffff8008510768>] platform_drv_probe+0x58/0xd0\n[    3.114599] c0 [<ffffff800850de2c>] driver_probe_device+0x1e8/0x470\n[    3.120830] c0 [<ffffff800850e168>] __driver_attach+0xb4/0xb8\n[    3.126541] c0 [<ffffff800850b750>] bus_for_each_dev+0x6c/0xac\n[    3.132339] c0 [<ffffff800850d6c0>] driver_attach+0x2c/0x34\n[    3.137877] c0 [<ffffff800850d234>] bus_add_driver+0x210/0x298\n[    3.143676] c0 [<ffffff800850f1f4>] driver_register+0x7c/0x114\n[    3.149476] c0 [<ffffff8008510654>] __platform_driver_register+0x60/0x6c\n[    3.156139] c0 [<ffffff8008f49f40>] sprd_cpufreq_platdrv_init+0x18/0x20\n[    3.162714] c0 [<ffffff8008082a64>] do_one_initcall+0xd0/0x1d8\n[    3.168514] c0 [<ffffff8008f0bc58>] kernel_init_freeable+0x1fc/0x29c\n[    3.174834] c0 [<ffffff8008ab554c>] kernel_init+0x20/0x12c\n[    3.180281] c0 [<ffffff8008086290>] ret_from_fork+0x10/0x40\n\nReported-by: Ke Wang <ke.wang@spreadtrum.com>\nSigned-off-by: Juri Lelli <juri.lelli@arm.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/3fdaf94d6250a82bcabe71bc9b4661a7ed1357c5"},{"sha":"bb7a198f7b6761d189ab4d5411946364535c4226","author":{"name":"Brendan Jackman","email":"9a0e2fce45c43ecf5e7457c4f206a85a06aae4fc@arm.com"},"message":"DEBUG: sched/fair: Fix missing sched_load_avg_cpu events\n\nupdate_cfs_rq_load_avg is called from update_blocked_averages without triggering\nthe sched_load_avg_cpu event. Move the event trigger to inside\nupdate_cfs_rq_load_avg to avoid this missing event.\n\nChange-Id: I6c4f66f687a644e4e7f798db122d28a8f5919b7b\nSigned-off-by: Brendan Jackman <brendan.jackman@arm.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/bb7a198f7b6761d189ab4d5411946364535c4226"},{"sha":"0842e4e342ecdf014c00b6b9785c527bed77b223","author":{"name":"Brendan Jackman","email":"9a0e2fce45c43ecf5e7457c4f206a85a06aae4fc@arm.com"},"message":"DEBUG: sched/fair: Fix sched_load_avg_cpu events for task_groups\n\nThe current sched_load_avg_cpu event traces the load for any cfs_rq that is\nupdated. This is not representative of the CPU load - instead we should only\ntrace this event when the cfs_rq being updated is in the root_task_group.\n\nChange-Id: I345c2f13f6b5718cb4a89beb247f7887ce97ed6b\nSigned-off-by: Brendan Jackman <brendan.jackman@arm.com>\nSigned-off-by: ahmedradaideh <ahmed.radaideh@gmail.com>","distinct":true,"url":"https://api.github.com/repos/ahmedradaideh/msm-3.18-eas/commits/0842e4e342ecdf014c00b6b9785c527bed77b223"}]}
{"actor":{"display_login":"ahmedradaideh"}}