{"push_id":549075679,"size":21,"distinct_size":21,"ref":"refs/heads/lk-lp","head":"d123d5503815676d15809e9db5513c53f6d864cb","before":"85b58e463496c0909b433cf31cb6d8dff22c1982","commits":[{"sha":"133bf1eb37a8b3187e237bfbdff8500ac32e40c0","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"qseecom: Check if ce clock is enabled before sending cmd to TZ\n\nMake change to check if ce clock is enabled before sending command\nto TZ, then to prevent data aborting if clock is not enabled for\nTZ crypto operation.\n\nCRs-Fixed: 726840\nChange-Id: I55b5b10ad80e741c39f8cf411f67e6b83887f3bb\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/133bf1eb37a8b3187e237bfbdff8500ac32e40c0"},{"sha":"67143f5c7d2105e8f1d22c802524e28e56fc4f0b","author":{"email":"f170b3970e1ff8de8ac083ab81eba96499e5ab96@codeaurora.org","name":"Zhen Kong"},"message":"qseecom: Enable/disable clock for client if bus scaling is not enabled\n\nTo avoid the service failure on a target where bus scaling flag is not\nenabled in target device tree file by mistake, make a change to enable/\ndisable crypto clocks when the client calls to scale up bus bandwidth\nand send command even if bus scaling feature is not enabled.\n\nCRs-Fixed: 726840\nChange-Id: Ib33a535051b68561bde5ab6a23ad0f02dc27ab13\nSigned-off-by: Zhen Kong <zkong@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/67143f5c7d2105e8f1d22c802524e28e56fc4f0b"},{"sha":"da6c572965de60accc72209954f51e70526eef39","author":{"email":"acf1f709dafbae362ae39414203bf1007742619a@codeaurora.org","name":"Mona Hossain"},"message":"qseecom: Add boundary checks for offset within message.\n\nQseecom driver does not have boundary checks for offset within the\nmessage. So this patch add checks to validate the offsets sent by\nclient to modify data within the command request message and it\nshould not exceed the memory allocated for that message.\n\nChange-Id: I29bfbdc154eebb4f3f4bfbb31789562e37fa5886\nSigned-off-by: Mona Hossain <mhossain@codeaurora.org>\nSigned-off-by: Mallikarjuna Reddy Amireddy <mamire@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/da6c572965de60accc72209954f51e70526eef39"},{"sha":"d3dbe8fd9b7558ae70d427f1561b753cb7bf40bf","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"f2fs: updated to \"pids_lock can be static\"","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/d3dbe8fd9b7558ae70d427f1561b753cb7bf40bf"},{"sha":"6f919394f6b233204739db2de371414f00d35e8c","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"ARM: pull in <asm/simd.h> from asm-generic\n\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/6f919394f6b233204739db2de371414f00d35e8c"},{"sha":"43666d60e6838d994409f9066efebc43b52f893f","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"ramdisk: restorecon governor sysfs nodes to u:object_r:sysfs_devices_system_cpu:s0\n\n* thanks to sykopompos\n* still needs to fix the case when governor changes","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/43666d60e6838d994409f9066efebc43b52f893f"},{"sha":"598630fbcd38ab876ad66e1bbd8b0ea4cf787167","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"ramdisk: set proper file permissions when uevent triggers","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/598630fbcd38ab876ad66e1bbd8b0ea4cf787167"},{"sha":"16a5138c5911ad5735ab925bc7d65b3337865da5","author":{"email":"e642b69ed2fc111e09ffdc37feb733a52253340d@oracle.com","name":"Sasha Levin"},"message":"KEYS: close race between key lookup and freeing\n\nWhen a key is being garbage collected, it's key->user would get put before\nthe ->destroy() callback is called, where the key is removed from it's\nrespective tracking structures.\n\nThis leaves a key hanging in a semi-invalid state which leaves a window open\nfor a different task to try an access key->user. An example is\nfind_keyring_by_name() which would dereference key->user for a key that is\nin the process of being garbage collected (where key->user was freed but\n->destroy() wasn't called yet - so it's still present in the linked list).\n\nThis would cause either a panic, or corrupt memory.\n\nChange-Id: Ic74246dc2dcc593f04f71063e3301e7356d588b7\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>\n\nConflicts:\n\tsecurity/keys/gc.c","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/16a5138c5911ad5735ab925bc7d65b3337865da5"},{"sha":"8e8e453b71e4767320f3383c4d3a97ca85a29990","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"cpufreq: do not remove sysfs nodes during governor exit\n\n* there shouldn't be any negative impact in doing this and solves\nfile permission and selinux context issues during switch","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/8e8e453b71e4767320f3383c4d3a97ca85a29990"},{"sha":"53c0c1e1cd7053b742fc0108a9ef83023f8c6988","author":{"email":"e4b2d9917bc51c00939020277d9154b44ab7b287@marvell.com","name":"Jane Li"},"message":"cpufreq: Fix timer/workqueue corruption by protecting reading governor_enabled\n\nWhen a CPU is hot removed we'll cancel all the delayed work items via\ngov_cancel_work(). Sometimes the delayed work function determines that\nit should adjust the delay for all other CPUs that the policy is\nmanaging. If this scenario occurs, the canceling CPU will cancel its own\nwork but queue up the other CPUs works to run.\n\nCommit 3617f2 (cpufreq: Fix timer/workqueue corruption due to double\nqueueing) has tried to fix this, but reading governor_enabled is not\nprotected by cpufreq_governor_lock. Even though od_dbs_timer() checks\ngovernor_enabled before gov_queue_work(), this scenario may occur. For\nexample:\n\n CPU0                                        CPU1\n ----                                        ----\n cpu_down()\n  ...                                        <work runs>\n  __cpufreq_remove_dev()                     od_dbs_timer()\n   __cpufreq_governor()                       policy->governor_enabled\n    policy->governor_enabled = false;\n    cpufreq_governor_dbs()\n     case CPUFREQ_GOV_STOP:\n      gov_cancel_work(dbs_data, policy);\n       cpu0 work is canceled\n        timer is canceled\n        cpu1 work is canceled\n        <waits for cpu1>\n                                              gov_queue_work(*, *, true);\n                                               cpu0 work queued\n                                               cpu1 work queued\n                                               cpu2 work queued\n                                               ...\n        cpu1 work is canceled\n        cpu2 work is canceled\n        ...\n\nAt the end of the GOV_STOP case cpu0 still has a work queued to\nrun although the code is expecting all of the works to be\ncanceled. __cpufreq_remove_dev() will then proceed to\nre-initialize all the other CPUs works except for the CPU that is\ngoing down. The CPUFREQ_GOV_START case in cpufreq_governor_dbs()\nwill trample over the queued work and debugobjects will spit out\na warning:\n\nWARNING: at lib/debugobjects.c:260 debug_print_object+0x94/0xbc()\nODEBUG: init active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x14\nModules linked in:\nCPU: 1 PID: 1205 Comm: sh Tainted: G        W    3.10.0 #200\n[<c01144f0>] (unwind_backtrace+0x0/0xf8) from [<c0111d98>] (show_stack+0x10/0x14)\n[<c0111d98>] (show_stack+0x10/0x14) from [<c01272cc>] (warn_slowpath_common+0x4c/0x68)\n[<c01272cc>] (warn_slowpath_common+0x4c/0x68) from [<c012737c>] (warn_slowpath_fmt+0x30/0x40)\n[<c012737c>] (warn_slowpath_fmt+0x30/0x40) from [<c034c640>] (debug_print_object+0x94/0xbc)\n[<c034c640>] (debug_print_object+0x94/0xbc) from [<c034c7f8>] (__debug_object_init+0xc8/0x3c0)\n[<c034c7f8>] (__debug_object_init+0xc8/0x3c0) from [<c01360e0>] (init_timer_key+0x20/0x104)\n[<c01360e0>] (init_timer_key+0x20/0x104) from [<c04872ac>] (cpufreq_governor_dbs+0x1dc/0x68c)\n[<c04872ac>] (cpufreq_governor_dbs+0x1dc/0x68c) from [<c04833a8>] (__cpufreq_governor+0x80/0x1b0)\n[<c04833a8>] (__cpufreq_governor+0x80/0x1b0) from [<c0483704>] (__cpufreq_remove_dev.isra.12+0x22c/0x380)\n[<c0483704>] (__cpufreq_remove_dev.isra.12+0x22c/0x380) from [<c0692f38>] (cpufreq_cpu_callback+0x48/0x5c)\n[<c0692f38>] (cpufreq_cpu_callback+0x48/0x5c) from [<c014fb40>] (notifier_call_chain+0x44/0x84)\n[<c014fb40>] (notifier_call_chain+0x44/0x84) from [<c012ae44>] (__cpu_notify+0x2c/0x48)\n[<c012ae44>] (__cpu_notify+0x2c/0x48) from [<c068dd40>] (_cpu_down+0x80/0x258)\n[<c068dd40>] (_cpu_down+0x80/0x258) from [<c068df40>] (cpu_down+0x28/0x3c)\n[<c068df40>] (cpu_down+0x28/0x3c) from [<c068e4c0>] (store_online+0x30/0x74)\n[<c068e4c0>] (store_online+0x30/0x74) from [<c03a7308>] (dev_attr_store+0x18/0x24)\n[<c03a7308>] (dev_attr_store+0x18/0x24) from [<c0256fe0>] (sysfs_write_file+0x100/0x180)\n[<c0256fe0>] (sysfs_write_file+0x100/0x180) from [<c01fec9c>] (vfs_write+0xbc/0x184)\n[<c01fec9c>] (vfs_write+0xbc/0x184) from [<c01ff034>] (SyS_write+0x40/0x68)\n[<c01ff034>] (SyS_write+0x40/0x68) from [<c010e200>] (ret_fast_syscall+0x0/0x48)\n\nIn gov_queue_work(), lock cpufreq_governor_lock before gov_queue_work,\nand unlock it after __gov_queue_work(). In this way, governor_enabled\nis guaranteed not changed in gov_queue_work().\n\nSigned-off-by: Jane Li <jiel@marvell.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/53c0c1e1cd7053b742fc0108a9ef83023f8c6988"},{"sha":"d2c52a86ae1998e1869623f34c631f7e8537c33d","author":{"email":"2ab1abb4425a1076fb72949b41346e3705590156@nvidia.com","name":"Bibek Basu"},"message":"cpufreq: remove race while accessing cur_policy\n\nWhile accessing cur_policy during executing events\nCPUFREQ_GOV_START, CPUFREQ_GOV_STOP, CPUFREQ_GOV_LIMITS,\nsame mutex lock is not taken, dbs_data->mutex, which leads\nto race and data corruption while running continious suspend\nresume test. This is seen with ondemand governor with suspend\nresume test using rtcwake.\n\n Unable to handle kernel NULL pointer dereference at virtual address 00000028\n pgd = ed610000\n [00000028] *pgd=adf11831, *pte=00000000, *ppte=00000000\n Internal error: Oops: 17 [#1] PREEMPT SMP ARM\n Modules linked in: nvhost_vi\n CPU: 1 PID: 3243 Comm: rtcwake Not tainted 3.10.24-gf5cf9e5 #1\n task: ee708040 ti: ed61c000 task.ti: ed61c000\n PC is at cpufreq_governor_dbs+0x400/0x634\n LR is at cpufreq_governor_dbs+0x3f8/0x634\n pc : [<c05652b8>] lr : [<c05652b0>] psr: 600f0013\n sp : ed61dcb0 ip : 000493e0 fp : c1cc14f0\n r10: 00000000 r9 : 00000000 r8 : 00000000\n r7 : eb725280 r6 : c1cc1560 r5 : eb575200 r4 : ebad7740\n r3 : ee708040 r2 : ed61dca8 r1 : 001ebd24 r0 : 00000000\n Flags: nZCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user\n Control: 10c5387d Table: ad61006a DAC: 00000015\n [<c05652b8>] (cpufreq_governor_dbs+0x400/0x634) from [<c055f700>] (__cpufreq_governor+0x98/0x1b4)\n [<c055f700>] (__cpufreq_governor+0x98/0x1b4) from [<c0560770>] (__cpufreq_set_policy+0x250/0x320)\n [<c0560770>] (__cpufreq_set_policy+0x250/0x320) from [<c0561dcc>] (cpufreq_update_policy+0xcc/0x168)\n [<c0561dcc>] (cpufreq_update_policy+0xcc/0x168) from [<c0561ed0>] (cpu_freq_notify+0x68/0xdc)\n [<c0561ed0>] (cpu_freq_notify+0x68/0xdc) from [<c008eff8>] (notifier_call_chain+0x4c/0x8c)\n [<c008eff8>] (notifier_call_chain+0x4c/0x8c) from [<c008f3d4>] (__blocking_notifier_call_chain+0x50/0x68)\n [<c008f3d4>] (__blocking_notifier_call_chain+0x50/0x68) from [<c008f40c>] (blocking_notifier_call_chain+0x20/0x28)\n [<c008f40c>] (blocking_notifier_call_chain+0x20/0x28) from [<c00aac6c>] (pm_qos_update_bounded_target+0xd8/0x310)\n [<c00aac6c>] (pm_qos_update_bounded_target+0xd8/0x310) from [<c00ab3b0>] (__pm_qos_update_request+0x64/0x70)\n [<c00ab3b0>] (__pm_qos_update_request+0x64/0x70) from [<c004b4b8>] (tegra_pm_notify+0x114/0x134)\n [<c004b4b8>] (tegra_pm_notify+0x114/0x134) from [<c008eff8>] (notifier_call_chain+0x4c/0x8c)\n [<c008eff8>] (notifier_call_chain+0x4c/0x8c) from [<c008f3d4>] (__blocking_notifier_call_chain+0x50/0x68)\n [<c008f3d4>] (__blocking_notifier_call_chain+0x50/0x68) from [<c008f40c>] (blocking_notifier_call_chain+0x20/0x28)\n [<c008f40c>] (blocking_notifier_call_chain+0x20/0x28) from [<c00ac228>] (pm_notifier_call_chain+0x1c/0x34)\n [<c00ac228>] (pm_notifier_call_chain+0x1c/0x34) from [<c00ad38c>] (enter_state+0xec/0x128)\n [<c00ad38c>] (enter_state+0xec/0x128) from [<c00ad400>] (pm_suspend+0x38/0xa4)\n [<c00ad400>] (pm_suspend+0x38/0xa4) from [<c00ac114>] (state_store+0x70/0xc0)\n [<c00ac114>] (state_store+0x70/0xc0) from [<c027b1e8>] (kobj_attr_store+0x14/0x20)\n [<c027b1e8>] (kobj_attr_store+0x14/0x20) from [<c019cd9c>] (sysfs_write_file+0x104/0x184)\n [<c019cd9c>] (sysfs_write_file+0x104/0x184) from [<c0143038>] (vfs_write+0xd0/0x19c)\n [<c0143038>] (vfs_write+0xd0/0x19c) from [<c0143414>] (SyS_write+0x4c/0x78)\n [<c0143414>] (SyS_write+0x4c/0x78) from [<c000f080>] (ret_fast_syscall+0x0/0x30)\n Code: e1a00006 eb084346 e59b0020 e5951024 (e5903028)\n ---[ end trace 0488523c8f6b0f9d ]---\n\nSigned-off-by: Bibek Basu <bbasu@nvidia.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nCc: 3.11+ <stable@vger.kernel.org> # 3.11+\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/d2c52a86ae1998e1869623f34c631f7e8537c33d"},{"sha":"566a97498fbf7f7150b3cc7e24a546a89677108f","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"cpufreq: governor: Be friendly towards latency-sensitive bursty workloads\n\nCpufreq governors like the ondemand governor calculate the load on the CPU\nperiodically by employing deferrable timers. A deferrable timer won't fire\nif the CPU is completely idle (and there are no other timers to be run), in\norder to avoid unnecessary wakeups and thus save CPU power.\n\nHowever, the load calculation logic is agnostic to all this, and this can\nlead to the problem described below.\n\nTime (ms)               CPU 1\n\n100                Task-A running\n\n110                Governor's timer fires, finds load as 100% in the last\n                   10ms interval and increases the CPU frequency.\n\n110.5              Task-A running\n\n120\t\t   Governor's timer fires, finds load as 100% in the last\n\t\t   10ms interval and increases the CPU frequency.\n\n125\t\t   Task-A went to sleep. With nothing else to do, CPU 1\n\t\t   went completely idle.\n\n200\t\t   Task-A woke up and started running again.\n\n200.5\t\t   Governor's deferred timer (which was originally programmed\n\t\t   to fire at time 130) fires now. It calculates load for the\n\t\t   time period 120 to 200.5, and finds the load is almost zero.\n\t\t   Hence it decreases the CPU frequency to the minimum.\n\n210\t\t   Governor's timer fires, finds load as 100% in the last\n\t\t   10ms interval and increases the CPU frequency.\n\nSo, after the workload woke up and started running, the frequency was suddenly\ndropped to absolute minimum, and after that, there was an unnecessary delay of\n10ms (sampling period) to increase the CPU frequency back to a reasonable value.\nAnd this pattern repeats for every wake-up-from-cpu-idle for that workload.\nThis can be quite undesirable for latency- or response-time sensitive bursty\nworkloads. So we need to fix the governor's logic to detect such wake-up-from-\ncpu-idle scenarios and start the workload at a reasonably high CPU frequency.\n\nOne extreme solution would be to fake a load of 100% in such scenarios. But\nthat might lead to undesirable side-effects such as frequency spikes (which\nmight also need voltage changes) especially if the previous frequency happened\nto be very low.\n\nWe just want to avoid the stupidity of dropping down the frequency to a minimum\nand then enduring a needless (and long) delay before ramping it up back again.\nSo, let us simply carry forward the previous load - that is, let us just pretend\nthat the 'load' for the current time-window is the same as the load for the\nprevious window. That way, the frequency and voltage will continue to be set\nto whatever values they were set at previously. This means that bursty workloads\nwill get a chance to influence the CPU frequency at which they wake up from\ncpu-idle, based on their past execution history. Thus, they might be able to\navoid suffering from slow wakeups and long response-times.\n\nHowever, we should take care not to over-do this. For example, such a \"copy\nprevious load\" logic will benefit cases like this: (where # represents busy\nand . represents idle)\n\n##########.........#########.........###########...........##########........\n\nbut it will be detrimental in cases like the one shown below, because it will\nretain the high frequency (copied from the previous interval) even in a mostly\nidle system:\n\n##########.........#.................#.....................#...............\n\n(i.e., the workload finished and the remaining tasks are such that their busy\nperiods are smaller than the sampling interval, which causes the timer to\nalways get deferred. So, this will make the copy-previous-load logic copy\nthe initial high load to subsequent idle periods over and over again, thus\nkeeping the frequency high unnecessarily).\n\nSo, we modify this copy-previous-load logic such that it is used only once\nupon every wakeup-from-idle. Thus if we have 2 consecutive idle periods, the\nprevious load won't get blindly copied over; cpufreq will freshly evaluate the\nload in the second idle interval, thus ensuring that the system comes back to\nits normal state.\n\n[ The right way to solve this whole problem is to teach the CPU frequency\ngovernors to also track load on a per-task basis, not just a per-CPU basis,\nand then use both the data sources intelligently to set the appropriate\nfrequency on the CPUs. But that involves redesigning the cpufreq subsystem,\nso this patch should make the situation bearable until then. ]\n\nExperimental results:\n+-------------------+\n\nI ran a modified version of ebizzy (called 'sleeping-ebizzy') that sleeps in\nbetween its execution such that its total utilization can be a user-defined\nvalue, say 10% or 20% (higher the utilization specified, lesser the amount of\nsleeps injected). This ebizzy was run with a single-thread, tied to CPU 8.\n\nBehavior observed with tracing (sample taken from 40% utilization runs):\n------------------------------------------------------------------------\n\nWithout patch:\n~~~~~~~~~~~~~~\nkworker/8:2-12137  416.335742: cpu_frequency: state=2061000 cpu_id=8\nkworker/8:2-12137  416.335744: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40753  416.345741: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-12137  416.345744: cpu_frequency: state=4123000 cpu_id=8\nkworker/8:2-12137  416.345746: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40753  416.355738: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\n<snip>  ---------------------------------------------------------------------  <snip>\n      <...>-40753  416.402202: sched_switch: prev_comm=ebizzy ==> next_comm=swapper/8\n     <idle>-0      416.502130: sched_switch: prev_comm=swapper/8 ==> next_comm=ebizzy\n      <...>-40753  416.505738: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-12137  416.505739: cpu_frequency: state=2061000 cpu_id=8\nkworker/8:2-12137  416.505741: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40753  416.515739: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-12137  416.515742: cpu_frequency: state=4123000 cpu_id=8\nkworker/8:2-12137  416.515744: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n\nObservation: Ebizzy went idle at 416.402202, and started running again at\n416.502130. But cpufreq noticed the long idle period, and dropped the frequency\nat 416.505739, only to increase it back again at 416.515742, realizing that the\nworkload is in-fact CPU bound. Thus ebizzy needlessly ran at the lowest frequency\nfor almost 13 milliseconds (almost 1 full sample period), and this pattern\nrepeats on every sleep-wakeup. This could hurt latency-sensitive workloads quite\na lot.\n\nWith patch:\n~~~~~~~~~~~\n\nkworker/8:2-29802  464.832535: cpu_frequency: state=2061000 cpu_id=8\n<snip>  ---------------------------------------------------------------------  <snip>\nkworker/8:2-29802  464.962538: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40738  464.972533: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-29802  464.972536: cpu_frequency: state=4123000 cpu_id=8\nkworker/8:2-29802  464.972538: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40738  464.982531: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\n<snip>  ---------------------------------------------------------------------  <snip>\nkworker/8:2-29802  465.022533: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40738  465.032531: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-29802  465.032532: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40738  465.035797: sched_switch: prev_comm=ebizzy ==> next_comm=swapper/8\n     <idle>-0      465.240178: sched_switch: prev_comm=swapper/8 ==> next_comm=ebizzy\n      <...>-40738  465.242533: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\nkworker/8:2-29802  465.242535: sched_switch: prev_comm=kworker/8:2 ==> next_comm=ebizzy\n      <...>-40738  465.252531: sched_switch: prev_comm=ebizzy ==> next_comm=kworker/8:2\n\nObservation: Ebizzy went idle at 465.035797, and started running again at\n465.240178. Since ebizzy was the only real workload running on this CPU,\ncpufreq retained the frequency at 4.1Ghz throughout the run of ebizzy, no\nmatter how many times ebizzy slept and woke-up in-between. Thus, ebizzy\ngot the 10ms worth of 4.1 Ghz benefit during every sleep-wakeup (as compared\nto the run without the patch) and this boost gave a modest improvement in total\nthroughput, as shown below.\n\nSleeping-ebizzy records-per-second:\n-----------------------------------\n\nUtilization  Without patch  With patch  Difference (Absolute and % values)\n    10%         274767        277046        +  2279 (+0.829%)\n    20%         543429        553484        + 10055 (+1.850%)\n    40%        1090744       1107959        + 17215 (+1.578%)\n    60%        1634908       1662018        + 27110 (+1.658%)\n\nA rudimentary and somewhat approximately latency-sensitive workload such as\nsleeping-ebizzy itself showed a consistent, noticeable performance improvement\nwith this patch. Hence, workloads that are truly latency-sensitive will benefit\nquite a bit from this change. Moreover, this is an overall win-win since this\npatch does not hurt power-savings at all (because, this patch does not reduce\nthe idle time or idle residency; and the high frequency of the CPU when it goes\nto cpu-idle does not affect/hurt the power-savings of deep idle states).\n\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nReviewed-by: Gautham R. Shenoy <ego@linux.vnet.ibm.com>\nAcked-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/566a97498fbf7f7150b3cc7e24a546a89677108f"},{"sha":"98e01d15363f1f8fce26339aa0a38026f596290a","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"cpufreq: governor: remove copy_prev_load from 'struct cpu_dbs_common_info'\n\n'copy_prev_load' was recently added by commit: 18b46ab (cpufreq: governor: Be\nfriendly towards latency-sensitive bursty workloads).\n\nIt actually is a bit redundant as we also have 'prev_load' which can store any\ninteger value and can be used instead of 'copy_prev_load' by setting it zero.\n\nTrue load can also turn out to be zero during long idle intervals (and hence the\nactual value of 'prev_load' and the overloaded value can clash). However this is\nnot a problem because, if the true load was really zero in the previous\ninterval, it makes sense to evaluate the load afresh for the current interval\nrather than copying the previous load.\n\nSo, drop 'copy_prev_load' and use 'prev_load' instead.\n\nUpdate comments as well to make it more clear.\n\nThere is another change here which was probably missed by Srivatsa during the\nlast version of updates he made. The unlikely in the 'if' statement was covering\nonly half of the condition and the whole line should actually come under it.\n\nAlso checkpatch is made more silent as it was reporting this (--strict option):\n\nCHECK: Alignment should match open parenthesis\n+\t\tif (unlikely(wall_time > (2 * sampling_rate) &&\n+\t\t\t\t\t\tj_cdbs->prev_load)) {\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nAcked-by: Pavel Machek <pavel@ucw.cz>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/98e01d15363f1f8fce26339aa0a38026f596290a"},{"sha":"656a2c41fd455e29e4f4d68fdd1ea1197e42b9e8","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"ramdisk: lkconfig: add option to drop caches to free up RAM for apps\n\n* pagecache, dentries and inodes","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/656a2c41fd455e29e4f4d68fdd1ea1197e42b9e8"},{"sha":"6890a824464174f59a11bc988d9021994b24820f","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"selinux: add force_audit sysfs node to enable logging of dontaudit\n\n* for kernel selinux debugging\n\n* to enable:\n* echo Y > /sys/module/selinux/parameters/force_audit","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/6890a824464174f59a11bc988d9021994b24820f"},{"sha":"0ccf74715777c14c823a6c581219522b6465ee4a","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"ramdisk: more selinux fixes including CM theme engine fix","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/0ccf74715777c14c823a6c581219522b6465ee4a"},{"sha":"10e43d26607472492f9dad088c778c050ff6a0b8","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"Linux 3.10.65","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/10e43d26607472492f9dad088c778c050ff6a0b8"},{"sha":"602f04986d3521b43fa04542e09f921777528246","author":{"email":"4bb1064d1f46929ded0070376617aece30f0ee54@google.com","name":"Mark Salyzyn"},"message":"[PATCH 5/5] pstore: selinux: add security in-core xattr support for pstore and debugfs\n\n- add \"pstore\" and \"debugfs\" to list of in-core exceptions\n- change fstype checks to boolean equation\n- change from strncmp to strcmp for checking\n\nSigned-off-by: Mark Salyzyn <salyzyn@google.com>\nBug: 18917345\nBug: 18935184\nChange-Id: Ib648f30ce4b5d6c96f11465836d6fee89bec1c72","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/602f04986d3521b43fa04542e09f921777528246"},{"sha":"8cf1e9d5ea129a1b771874f0e24a9e49af26d368","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"Revert \"pstore-ram: Allow optional mapping with pgprot_noncached\"\n\nThis reverts commit c0d9d658fa9410fa8f4a8b7eb216f236102f02f2.\n\n* not compatible with motorola's changes","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/8cf1e9d5ea129a1b771874f0e24a9e49af26d368"},{"sha":"d815dcfcc73b2bb6860f1a22bb2210ee5ce4296e","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"ramdisk: reclaim a bit more memory for apps from dir/file caches","distinct":true,"url":"https://api.github.com/repos/imoseyon/leanKernel-shamu/commits/d815dcfcc73b2bb6860f1a22bb2210ee5ce4296e"}]}