{"push_id":953703185,"size":12,"distinct_size":12,"ref":"refs/heads/cm-13.0","head":"2b618ae2b45a1a4aa1918eec4ea988bf3c28d4f4","before":"dfc71edaa0764c6f6075fe63cc0162b3204ee798","commits":[{"sha":"da0e75fb4e50a732d48601515dc89b4b35219dcc","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"Revert \"tracing/sched: Track per-cpu rt and non-rt cpu_load.\"\n\nThis reverts commit 4dc47fb113fee708933e503f96c3c6345678088d.\n\nChange-Id: I916a4dc63acdbc0c4bb7a72d62a2fa2a2dfc0cb2","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/da0e75fb4e50a732d48601515dc89b4b35219dcc"},{"sha":"2197122250ac3d399b356d6a44c9f0b2ae8d6fdc","author":{"email":"36c70fbf4b52b53dfac53874339f0dd2ccc58e23@suse.de","name":"Mike Galbraith"},"message":"sched: Fix migration thread runtime bogosity\n\ncommit 8f6189684eb4e85e6c593cd710693f09c944450a upstream.\n\nMake stop scheduler class do the same accounting as other classes,\n\nMigration threads can be caught in the act while doing exec balancing,\nleading to the below due to use of unmaintained ->se.exec_start.  The\nload that triggered this particular instance was an apparently out of\ncontrol heavily threaded application that does system monitoring in\nwhat equated to an exec bomb, with one of the VERY frequently migrated\ntasks being ps.\n\n%CPU   PID USER     CMD\n99.3    45 root     [migration/10]\n97.7    53 root     [migration/12]\n97.0    57 root     [migration/13]\n90.1    49 root     [migration/11]\n89.6    65 root     [migration/15]\n88.7    17 root     [migration/3]\n80.4    37 root     [migration/8]\n78.1    41 root     [migration/9]\n44.2    13 root     [migration/2]\n\nChange-Id: Id397924dfdc6c16dfdc6d1d0aba871300f28314a\nSigned-off-by: Mike Galbraith <mgalbraith@suse.de>\nSigned-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>\nLink: http://lkml.kernel.org/r/1344051854.6739.19.camel@marge.simpson.net\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/2197122250ac3d399b356d6a44c9f0b2ae8d6fdc"},{"sha":"3023e3972887262aaf3cea8d8dbdcff87c418c51","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: Make scheduler aware of cpu frequency state\n\nCapacity of a cpu (how much performance it can deliver) is partly\ndetermined by its frequency (P) state, both current frequency as well\nas max frequency it can reach.  Knowing frequency state of cpus will\nhelp scheduler optimize various functions such as tracking every\ntask's cpu demand and placing tasks on various cpus.\n\nThis patch has scheduler registering for cpufreq notifications to\nbecome aware of cpu's frequency state. Subsequent patches will make\nuse of derived information for various purposes, such as task's scaled\nload (cpu demand) accounting and task placement.\n\nChange-Id: I376dffa1e7f3f47d0496cd7e6ef8b5642ab79016\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/3023e3972887262aaf3cea8d8dbdcff87c418c51"},{"sha":"ab23d2722af706554294fe1b5f4b01bac51a88e5","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: window-based load stats for tasks\n\nProvide a metric per task that specifies how cpu bound a task is. Task\nexecution is monitored over several time windows and the fraction of\nthe window for which task was found to be executing or wanting to run\nis recorded as task's demand. Windows over which task was sleeping are\nignored. We track last 5 recent windows for every task and the maximum\ndemand seen in any of the previous 5 windows (where task had some\nactivity) drives freq demand for every task.\n\nA per-cpu metric (rq->cumulative_runnable_avg) is also provided which\nis an aggregation of cpu demand of all tasks currently enqueued on it.\nrq->cumulative_runnable_avg will be useful to know if cpu frequency\nwill need to be changed to match task demand.\n\nChange-Id: Ib83207b9ba8683cd3304ee8a2290695c34f08fe2\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/ab23d2722af706554294fe1b5f4b01bac51a88e5"},{"sha":"b16d42d2e68af336403e29003bbfb2ecc9978b19","author":{"email":"9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","name":"Rohit Gupta"},"message":"sched: Call the notify_on_migrate notifier chain for wakeups as well\n\nAdd a change to send notify_on_migrate hints on wakeups of\nforeground tasks from scheduler if their load is above\nwakeup_load_thresholds (default value is 60).\nThese hints can be used to choose an appropriate CPU frequency\ncorresponding to the load of the task being woken up.\n\nChange-Id: Ieca413c1a8bd2b14a15a7591e8e15d22925c42ca\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/b16d42d2e68af336403e29003bbfb2ecc9978b19"},{"sha":"a1cb5ee3e8d53f233d3389ecb55a921f57ec3d87","author":{"email":"9296a0ca31e8299ed6ec39daa4ff56fd47a51cb6@codeaurora.org","name":"Rohit Gupta"},"message":"sched: Disable wakeup hints for foreground tasks by default\n\nBy default sched_wakeup_load_threshold is set to 60 and therefore\nwakeup hints are sent out for those tasks whose loads are higher\nthat value. This might cause unnecessary wakeup boosts to happen\nwhen load based syncing is turned ON for cpu-boost.\nDisable the wake up hints by setting the sched_wakeup_load_threshold\nto a value higher than 100 so that wakeup boost doesnt happen unless\nit is explicitly turned ON from adb shell.\n\nChange-Id: I9b8a594c2bfdf2e092cc645e50c0c21efc514c2f\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/a1cb5ee3e8d53f233d3389ecb55a921f57ec3d87"},{"sha":"c59e53298d7a009e22c8e23255ef673858f97969","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: Window-based load stat improvements\n\nSome tasks can have a sporadic load pattern such that they can suddenly\nstart running for longer intervals of time after running for shorter\ndurations. To recognize such sharp increase in tasks' demands, max\nbetween the average of 5 window load samples and the most recent sample\nis chosen as the task demand.\n\nMake the window size (sched_ravg_window) configurable at boot up\ntime. To prevent users from setting inappropriate values for window\nsize, min and max limits are defined. As 'ravg' struct tracks load for\nboth real-time and non real-time tasks it is moved out of sched_entity\nstruct.\n\nIn order to prevent changing function signatures for move_tasks() and\nmove_one_task() per-cpu variables are defined to track the total load\nmoved. In case multiple tasks are selected to migrate in one load\nbalance operation, loads > 100 could be sent through migration notifiers.\nPrevent this scenario by setting mnd.load to 100 in such cases.\n\nDefine wrapper functions to compute cpu demands for tasks and to change\nrq->cumulative_runnable_avg.\n\nChange-Id: I9abfbf3b5fe23ae615a6acd3db9580cfdeb515b4\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>\nSigned-off-by: Rohit Gupta <rohgup@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/c59e53298d7a009e22c8e23255ef673858f97969"},{"sha":"ba6b5d42638a8e835ab65df8ef2a49e66744fc89","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: window-stats: Fix overflow bug\n\nMultiplication over-flow possibility exists in update_task_ravg() when\nupdating task's window_start. That would lead to incorrect accounting\nof task load. Fix the issue by using 64-bit arithmetic.\n\nCRs-Fixed: 665706\nChange-Id: I92651c41efa6121bb8fe102e495ae956127b237a\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/ba6b5d42638a8e835ab65df8ef2a49e66744fc89"},{"sha":"55e7b4736f715d58f98cf1a210d05915275ba268","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: Skip load update for idle task\n\nLoad statistics for idle tasks is not useful in any manner. Skip load\nupdate for such idle tasks.\n\nCRs-Fixed: 665706\nChange-Id: If3a908bad7fbb42dcb3d0a1d073a3750cf32fcf9\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/55e7b4736f715d58f98cf1a210d05915275ba268"},{"sha":"8ddf4031c11a270fc4aefc88fbb3a34a4f0cc288","author":{"email":"d282495bfb62d367009a66784cabed6d13acc2f2@codeaurora.org","name":"Steve Muckle"},"message":"sched: move task load based functions\n\nThe task load based functions will need to make use of LOAD_AVG_MAX\nin a subsequent patch, so move them below the definition of that\nmacro.\n\nChange-Id: I02f18ba069b81033e611f8f8bba6dccd7cd81252\nSigned-off-by: Steve Muckle <smuckle@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/8ddf4031c11a270fc4aefc88fbb3a34a4f0cc288"},{"sha":"bfa87246637644f734815c93313794935c1cb1b0","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: Add min_max_freq and rq->max_possible_freq\n\nrq->max_possible_freq represents the maximum frequency a cpu is\ncapable of attaining, while rq->max_freq represents the maximum\nfrequency a cpu can attain at a given instant. rq->max_freq includes\nconstraints imposed by user or thermal driver.\nrq->max_freq <= rq->max_possible_freq.\n\nmax_possible_freq is derived as max(rq->max_possible_freq) and\nrepresents the \"best\" cpu that can attain best possible frequency.\n\nmin_max_freq is derived as min(rq->max_possible_freq). For homogeneous\nsystems, max_possible_freq and min_max_freq will be same, while they\ncould be different on heterogeneous systems.\n\nChange-Id: Iec485fde35cfd33f55ebf2c2dce4864faa2083c5\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/bfa87246637644f734815c93313794935c1cb1b0"},{"sha":"2b618ae2b45a1a4aa1918eec4ea988bf3c28d4f4","author":{"email":"69d4c67d027719823df1f8f9226c47bc05dc8998@codeaurora.org","name":"Srivatsa Vaddagiri"},"message":"sched: window-based load stats improvements\n\nFollowing cleanups and improvements are made to window-based load\nstats feature:\n\n* Add sysctl to pick max, avg or most recent samples as task's\n  demand.\n\n* Fix overflow possibility in calculation of sum for average policy.\n\n* Use unscaled statistics when a task is running on a CPU which is\nthermally throttled.\n\nChange-Id: I8293565ca0c2a785dadf8adb6c67f579a445ed29\nSigned-off-by: Srivatsa Vaddagiri <vatsa@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/nx503a-dev/android_kernel_zte_nx503a/commits/2b618ae2b45a1a4aa1918eec4ea988bf3c28d4f4"}]}