{"push_id":1085328512,"size":35,"distinct_size":35,"ref":"refs/heads/cm-13.0","head":"ab56af0c2d0ff00588cae1d41c498fb6af2e541f","before":"c88755ff310b6c6cc648688d1f68933f59837e39","commits":[{"sha":"535f8dffc982e31ba2f6bc0341b2a9e1da607e33","author":{"email":"f716b4e7fb105b3b5ce1d7f1d4213769d3b27187@codeaurora.org","name":"Lucille Sylvester"},"message":"msm: kgsl: Bump the GPU frequency for long blocks of processing\n\nIf there are several frames of full GPU utilization immediately\nbump the frequency to turbo rather than waiting for the DCVS\nalgorithm to run.\n\nChange-Id: I1215225f8903a8656e8ad92c6c82567b86665933\nSigned-off-by: Lucille Sylvester <lsylvest@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/535f8dffc982e31ba2f6bc0341b2a9e1da607e33"},{"sha":"481c117cff50fa16825444515cb3a645feeb3c99","author":{"email":"fec53db8c4887e6e95defbb5052bc6438029c1e6@codeaurora.org","name":"Jordan Crouse"},"message":"msm: kgsl: Elevate the priority of the thread during adreno start\n\nIt turns out that having lots of spurious threads causes race\nconditions. Who knew? Instead of spawning a new high prority\nthread just bump the priority of the current thread up\nwhile adreno_start is running.\n\nChange-Id: Ic0dedbadf65da11c800578c8769ae844f010e925\nSigned-off-by: Jordan Crouse <jcrouse@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/481c117cff50fa16825444515cb3a645feeb3c99"},{"sha":"5bda12cd901aedf8d4676a67e1b5d1b5e32a80e1","author":{"email":"ce25c3cee4cc6c4c8acfc1680b3ed89cf644dba3@codeaurora.org","name":"Saravana Kannan"},"message":"PM / devfreq: Rewrite devfreq_update_status() to fix multiple bugs\n\nThe current devfreq_update_status() has the following bugs:\n- When the new frequency doesn't have a valid level, the time spent in the\n  new frequency is counted towards the next valid frequency switch instead\n  of being ignored.\n- The time spent on the previous frequency is added to the new frequency's\n  stats instead of the previous frequency's stats.\n\nThis patch fixes all of this.\n\nChange-Id: I7bbdafca78d1565cdbf815356556fe6d6cca9e3f\nSigned-off-by: Saravana Kannan <skannan@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/5bda12cd901aedf8d4676a67e1b5d1b5e32a80e1"},{"sha":"fe4c31c610d583a66e4bb7a78231807549333654","author":{"email":"a1418a03e3f7813c1fd3f97ab13f9d68ba5a9ac2@gmail.com","name":"Evisceration"},"message":"fs: fsync: correct permissions, cleanup introduced whitespaces\n\nChange-Id: I0203417e3bd36d559b86c800800a7f7dcd090e07","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/fe4c31c610d583a66e4bb7a78231807549333654"},{"sha":"946328739dc74fcc9ae6d48ba09951e96a66eb21","author":{"email":"06c4bad688863c93f06a8196fa754f5b50238e6f@gmail.com","name":"Tk-Glitch"},"message":"sched: Add sysinterface for GENTLE_FAIR_SLEEPERS\n\nChange-Id: Ie9a5e9fdd1dea869019081af0d6e540af79518ac","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/946328739dc74fcc9ae6d48ba09951e96a66eb21"},{"sha":"1f4c271ea4281bc01b52556de3a296af021754e2","author":{"email":"d688953a19dcb476c5fb90e6abba87f77b09be65@gmail.com","name":"Pranav Vashi"},"message":"sched: Add controls for sched features\n\n* Currently we provide users attributes to enable/\n  disable GENTLE_FAIR_SLEEPERS and ARCH_POWER\n* This patch uses already implemented GFS structure\n  to add ARCH_POWER attribute.\n* Attributes can be found under /sys/kernel/sched/*\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tkernel/ksysfs.c","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/1f4c271ea4281bc01b52556de3a296af021754e2"},{"sha":"5717a111130e16da93b23954222c747fd51c656d","author":{"email":"aaf6fd97230863eae371b8b6c4c40693d5d84b30@bynet.co.il","name":"Dorimanx"},"message":"Disable gentle_fair_sleepers and arch_power by default.\n\nWhen using ARCH Power we get more battery drain, and instability.\n\nabout gentle_fair_sleepers:\n\na) GENTLE FAIR SLEEPERS\n\nSignificance: Android UI Interactivity.\n\nSleeper Fairness is a concept used by CFS which treat sleeping/waiting tasks as if they were in a run queue.\nThis implies tasks which spend most of the time waiting for an user input and such will get a fair share of CPU when they need it.\n\nDisabling Gentle Fair Sleepers could improve UI responsiveness.\n\nb) ARCH POWER\n\nSignificance: ARM Topology Awareness.\n\nArch Power patch causes arch dependent power functions to be used instead of generic high resolution timer ticks and double ticks.\n\nAlso set sysfs control to read only. if i will want to test i will set 644 on it.\n\nConflicts:\n\tkernel/sched/fair.c","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/5717a111130e16da93b23954222c747fd51c656d"},{"sha":"199e604dce4a5fb3d6a89c282632adc82b1cc91b","author":{"email":"602733bbf830274d69620a4044352b6860a52d50@gmail.com","name":"DerRomtester"},"message":"ksysfs: change permissions of arch power and gentle fair sleepers\n\nSigned-off-by: DerRomtester <dieb.stefan.96@gmail.com>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/199e604dce4a5fb3d6a89c282632adc82b1cc91b"},{"sha":"f347408f5800b1d3c8cb9853c8162ecd376274aa","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"fs/namei.c: fix potential memory leak in path_lookupat\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/f347408f5800b1d3c8cb9853c8162ecd376274aa"},{"sha":"d62bb0ef1de9aae3f79a8d6c3ef425ddf49382bb","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"char: frandom: initial commit v1.1\n\n    Based on my dd test:\n      hw_random (msm_rng): 0.56 MB/s\n      linux random/urandom: 4.4 MB/s\n      frandom/erandom: 90 MB/s\n\nChange-Id: Ic2a9104777cc9fa6085732663d36435a3f520d83","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/d62bb0ef1de9aae3f79a8d6c3ef425ddf49382bb"},{"sha":"9ed5322ff0ca366f8489c02d4515c01b279c8f6d","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"random: entropy tweaks are all the rage nowadays\n\nuse nonblocking for all.  Read this web page:\nhttp://lwn.net/Articles/489734/\n\nChange-Id: Ia264a760cc3f5c51299d6620c56f1e71df0d391a","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/9ed5322ff0ca366f8489c02d4515c01b279c8f6d"},{"sha":"7c7ffc9f5b9ceeb245dccf1b08611db809ed4aa3","author":{"email":"742cc7da48fa788d384ec77ccfb9a4657661404c@gmail.com","name":"imoseyon"},"message":"random: prevent add_input from doing anything\n\nChange-Id: I57af3608e50e3d16218cc9b3a010dc10f128bb17","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/7c7ffc9f5b9ceeb245dccf1b08611db809ed4aa3"},{"sha":"091842f88f79829b638a58cb55e88b05de75e38a","author":{"email":"8a453bad9912ffe59bc0f0b8abe03df9be19379e@linux.intel.com","name":"H. Peter Anvin"},"message":"random: Statically compute poolbitshift, poolbytes, poolbits\n\nFrom: \"H. Peter Anvin\" <hpa@linux.intel.com>\n\nUse a macro to statically compute poolbitshift (will be used in a\nsubsequent patch), poolbytes, and poolbits.  On virtually all\narchitectures the cost of a memory load with an offset is the same as\nthe one of a memory load.\n\nIt is still possible for this to generate worse code since the C\ncompiler doesn't know the fixed relationship between these fields, but\nthat is somewhat unlikely.\n\nChange-Id: I6ba17ddb3b170cea4feefa1ad5459fe650bda666\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nCc: <stable@vger.kernel.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/091842f88f79829b638a58cb55e88b05de75e38a"},{"sha":"7400d635b8f5dc7b137400633e08f7ed342d87a4","author":{"email":"8a453bad9912ffe59bc0f0b8abe03df9be19379e@linux.intel.com","name":"H. Peter Anvin"},"message":"random: Account for entropy loss due to overwrites\n\nFrom: \"H. Peter Anvin\" <hpa@linux.intel.com>\n\nWhen we write entropy into a non-empty pool, we currently don't\naccount at all for the fact that we will probabilistically overwrite\nsome of the entropy in that pool.  This means that unless the pool is\nfully empty, we are currently *guaranteed* to overestimate the amount\nof entropy in the pool!\n\nAssuming Shannon entropy with zero correlations we end up with an\nexponentally decaying value of new entropy added:\n\n\tentropy <- entropy + (pool_size - entropy) *\n\t\t(1 - exp(-add_entropy/pool_size))\n\nHowever, calculations involving fractional exponentials are not\npractical in the kernel, so apply a piecewise linearization:\n\n\t  For add_entropy <= pool_size then\n\n\t  (1 - exp(-add_entropy/pool_size)) >= (add_entropy/pool_size)*0.632...\n\n\t  ... so we can approximate the exponential with\n\t  add_entropy/(pool_size*2) and still be on the\n\t  safe side by adding at most one pool_size at a time.\n\nIn order for the loop not to take arbitrary amounts of time if a bad\nioctl is received, terminate if we are within one bit of full.  This\nway the loop is guaranteed to terminate after no more than\nlog2(poolsize) iterations, no matter what the input value is.  The\nvast majority of the time the loop will be executed exactly once.\n\nThe piecewise linearization is very conservative, approaching 1/2 of\nthe usable input value for small inputs, however, our entropy\nestimation is pretty weak at best, especially for small values; we\nhave no handle on correlation; and the Shannon entropy measure (Réi\nentropy of order 1) is not the correct one to use in the first place,\nbut rather the correct entropy measure is the min-entropy, the Réi\nentropy of infinite order.\n\nAs such, this conservatism seems more than justified.  Note, however,\nthat attempting to add one bit of entropy will never succeed; nor will\ntwo bits unless the pool is completely empty.  These roundoff\nartifacts could be improved by using fixed-point arithmetic and adding\nsome number of fractional entropy bits.\n\n[ v2: rely on the previous patch for poolbitshift ]\n\nChange-Id: If89fbc57efc5586018d4407db92419aed71daced\nSigned-off-by: H. Peter Anvin <hpa@linux.intel.com>\nCc: DJ Johnston <dj.johnston@intel.com>\nCc: <stable@vger.kernel.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/7400d635b8f5dc7b137400633e08f7ed342d87a4"},{"sha":"f45bfeab678eea119d96091b6271c4b41cf62ec4","author":{"email":"a0e0bc655fdc6685e623efd3336a27ce1c465fa0@hotmail.de","name":"Blechd0se"},"message":"mach-msm: disable kernel-side mpdecision\n\nSigned-off-by: Blechd0se <alex.christ@hotmail.de>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/f45bfeab678eea119d96091b6271c4b41cf62ec4"},{"sha":"733028b0bb46dcd7cc1e1d003755f3cb0256c0e4","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"CPU hotplug: Provide lockless versions of callback registration functions\n\nThe following method of CPU hotplug callback registration is not safe\ndue to the possibility of an ABBA deadlock involving the cpu_add_remove_lock\nand the cpu_hotplug.lock.\n\n\tget_online_cpus();\n\n\tfor_each_online_cpu(cpu)\n\t\tinit_cpu(cpu);\n\n\tregister_cpu_notifier(&foobar_cpu_notifier);\n\n\tput_online_cpus();\n\nThe deadlock is shown below:\n\n          CPU 0                                         CPU 1\n          -----                                         -----\n\n   Acquire cpu_hotplug.lock\n   [via get_online_cpus()]\n\n                                              CPU online/offline operation\n                                              takes cpu_add_remove_lock\n                                              [via cpu_maps_update_begin()]\n\n   Try to acquire\n   cpu_add_remove_lock\n   [via register_cpu_notifier()]\n\n                                              CPU online/offline operation\n                                              tries to acquire cpu_hotplug.lock\n                                              [via cpu_hotplug_begin()]\n\n                            *** DEADLOCK! ***\n\nThe problem here is that callback registration takes the locks in one order\nwhereas the CPU hotplug operations take the same locks in the opposite order.\nTo avoid this issue and to provide a race-free method to register CPU hotplug\ncallbacks (along with initialization of already online CPUs), introduce new\nvariants of the callback registration APIs that simply register the callbacks\nwithout holding the cpu_add_remove_lock during the registration. That way,\nwe can avoid the ABBA scenario. However, we will need to hold the\ncpu_add_remove_lock throughout the entire critical section, to protect updates\nto the callback/notifier chain.\n\nThis can be achieved by writing the callback registration code as follows:\n\n\tcpu_maps_update_begin(); [ or cpu_notifier_register_begin(); see below ]\n\n\tfor_each_online_cpu(cpu)\n\t\tinit_cpu(cpu);\n\n\t/* This doesn't take the cpu_add_remove_lock */\n\t__register_cpu_notifier(&foobar_cpu_notifier);\n\n\tcpu_maps_update_done();  [ or cpu_notifier_register_done(); see below ]\n\nNote that we can't use get_online_cpus() here instead of cpu_maps_update_begin()\nbecause the cpu_hotplug.lock is dropped during the invocation of CPU_POST_DEAD\nnotifiers, and hence get_online_cpus() cannot provide the necessary\nsynchronization to protect the callback/notifier chains against concurrent\nreads and writes. On the other hand, since the cpu_add_remove_lock protects\nthe entire hotplug operation (including CPU_POST_DEAD), we can use\ncpu_maps_update_begin/done() to guarantee proper synchronization.\n\nAlso, since cpu_maps_update_begin/done() is like a super-set of\nget/put_online_cpus(), the former naturally protects the critical sections\nfrom concurrent hotplug operations.\n\nSince the names cpu_maps_update_begin/done() don't make much sense in CPU\nhotplug callback registration scenarios, we'll introduce new APIs named\ncpu_notifier_register_begin/done() and map them to cpu_maps_update_begin/done().\n\nIn summary, introduce the lockless variants of un/register_cpu_notifier() and\nalso export the cpu_notifier_register_begin/done() APIs for use by modules.\nThis way, we provide a race-free way to register hotplug callbacks as well as\nperform initialization for the CPUs that are already online.\n\nChange-Id: If62c2541afb3032da62ec8e4b8049ea51dbe823d\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Toshi Kani <toshi.kani@hp.com>\nCc: \"Rafael J. Wysocki\" <rjw@rjwysocki.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Ingo Molnar <mingo@kernel.org>\nAcked-by: Oleg Nesterov <oleg@redhat.com>\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nGit-commit: 93ae4f978ca7f26d17df915ac7afc919c1dd0353\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/733028b0bb46dcd7cc1e1d003755f3cb0256c0e4"},{"sha":"85a650b4490d63a8388d473454bb596f2390c40a","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"Doc/cpu-hotplug: Specify race-free way to register CPU hotplug callbacks\n\nRecommend the usage of the new CPU hotplug callback registration APIs\n(__register_cpu_notifier() etc), when subsystems need to also perform\ninitialization for already online CPUs. Provide examples of correct\nand race-free ways of achieving this, and point out the kinds of code\nthat are error-prone.\n\nChange-Id: I1693a7c4179cffd9a94c3eb46defe6d642587665\nCc: Rob Landley <rob@landley.net>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: linux-doc@vger.kernel.org\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nGit-commit: 8489d90b5f32effa402be2a4ee7636ba0c652145\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/85a650b4490d63a8388d473454bb596f2390c40a"},{"sha":"a9fc473e6c029fc3e35a7c0e4c73afe7522b26d4","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"perf, cpu hotplug: Run CPU_STARTING notifiers with irqs disabled\n\nThe CPU_STARTING notifiers are supposed to be run with irqs\ndisabled. But the perf_cpu_notifier() macro invokes them without\ndoing that. Fix it.\n\nChange-Id: Icaaf41e740e5a8ce1c95fa7c9b9c497c8a62d1fc\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nReviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: peterz@infradead.org\nCc: acme@ghostprotocols.net\nLink: http://lkml.kernel.org/r/20121016075809.3572.47848.stgit@srivatsabhat.in.ibm.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/a9fc473e6c029fc3e35a7c0e4c73afe7522b26d4"},{"sha":"c639ad3fdb12021b147ff8deb75149095d6a65d6","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"perf, cpu hotplug: Use cached value of smp_processor_id()\n\nThe perf_cpu_notifier() macro invokes smp_processor_id()\nmultiple times. Optimize it by using a local variable.\n\nChange-Id: I0dd94d91b4c58140119f469ddb286d434b444e20\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nReviewed-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: peterz@infradead.org\nCc: acme@ghostprotocols.net\nLink: http://lkml.kernel.org/r/20121016075817.3572.76733.stgit@srivatsabhat.in.ibm.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/c639ad3fdb12021b147ff8deb75149095d6a65d6"},{"sha":"0bb6add2d351d2ceb75094dd5088f273a0694ce5","author":{"email":"5b23f8226e886b22344fc642373ea657dd596b63@linux.vnet.ibm.com","name":"Srivatsa S. Bhat"},"message":"mm, vmstat: Fix CPU hotplug callback registration\n\nSubsystems that want to register CPU hotplug callbacks, as well as perform\ninitialization for the CPUs that are already online, often do it as shown\nbelow:\n\n\tget_online_cpus();\n\n\tfor_each_online_cpu(cpu)\n\t\tinit_cpu(cpu);\n\n\tregister_cpu_notifier(&foobar_cpu_notifier);\n\n\tput_online_cpus();\n\nThis is wrong, since it is prone to ABBA deadlocks involving the\ncpu_add_remove_lock and the cpu_hotplug.lock (when running concurrently\nwith CPU hotplug operations).\n\nInstead, the correct and race-free way of performing the callback\nregistration is:\n\n\tcpu_notifier_register_begin();\n\n\tfor_each_online_cpu(cpu)\n\t\tinit_cpu(cpu);\n\n\t/* Note the use of the double underscored version of the API */\n\t__register_cpu_notifier(&foobar_cpu_notifier);\n\n\tcpu_notifier_register_done();\n\nFix the vmstat code in the MM subsystem by using this latter form of callback\nregistration.\n\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Rik van Riel <riel@redhat.com>\nCc: Johannes Weiner <hannes@cmpxchg.org>\nCc: Cody P Schafer <cody@linux.vnet.ibm.com>\nCc: Toshi Kani <toshi.kani@hp.com>\nCc: Dave Hansen <dave@sr71.net>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: linux-mm@kvack.org\nAcked-by: Christoph Lameter <cl@linux.com>\nReviewed-by: Yasuaki Ishimatsu <isimatu.yasuaki@jp.fujitsu.com>\nSigned-off-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nGit-commit: 0be94bad0b601df94b8558c0cbd28f7e6633c9e8\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[osvaldob@codeaurora.org: resolve trivial context conflicts]\nSigned-off-by: Osvaldo Banuelos <osvaldob@codeaurora.org>\n\nChange-Id: Iac142a6e71e6f13e0fc854af18d796d5e7bfc42d","distinct":true,"url":"https://api.github.com/repos/CarlosArriagaCM/XInfinity_falcon/commits/0bb6add2d351d2ceb75094dd5088f273a0694ce5"}]}