{"push_id":2303997006,"size":12,"distinct_size":12,"ref":"refs/heads/minimal","head":"3132f0ebf7dc323ba5f0d2773d94f07c667009ec","before":"51673a318b38e5d0f00fd86c8b78809100bc6910","commits":[{"sha":"656057f7ff3517cabe1c3f51272a1688e7e4af00","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"usb: dwc3-msm: Don't issue power supply change for invalid charger\n\nThis is constantly causing wakeups and general havoc/instability, as it\nconstantly issues a power supply change for the same power supply type\n(DWC3_INVALID_CHARGER).\n\nConstantly issuing a power supply change for an invalid charger doesn't\nmake sense, so don't do it in order to fix the USB madness.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\nSigned-off-by: engstk <eng.stk@sapo.pt>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/656057f7ff3517cabe1c3f51272a1688e7e4af00"},{"sha":"3392fe0b2c8f70d223016cdcc443286ee714a05a","author":{"name":"FedericoBenedetti","email":"3e01b08cf0eb01d8a3a58185c693f15da8a713cc@gmail.com"},"message":"gemini: let's try with 1000HZ","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/3392fe0b2c8f70d223016cdcc443286ee714a05a"},{"sha":"16dd35ac488f8e9ef5afa6821ce6e87369c30879","author":{"name":"Syed Rameez Mustafa","email":"d0cb06bd5d626529e5ca7f6aba1e2023bbe2ea99@codeaurora.org"},"message":"cpu-hotplug: Always use real time scheduling when hotplugging a CPU\n\nCPU hotplug operations take place in preemptible context. This leaves\nthe hotplugging thread at the mercy of overall system load and CPU\navailability. If the hotplugging thread does not get an opportunity\nto execute after it has already begun a hotplug operation, CPUs can\nend up being stuck in a quasi online state. In the worst case a CPU\ncan be stuck in a state where the migration thread is parked while\nanother task is executing and changing affinity in a loop. This\ncombination can result in unbounded execution time for the running\ntask until the hotplugging thread gets the chance to run to complete\nthe hotplug operation.\n\nFix the said problem by ensuring that hotplug can only occur from\nthreads belonging to the RT sched class. This allows the hotplugging\nthread priority on the CPU no matter what the system load or the\nnumber of available CPUs are. If a SCHED_NORMAL task attempts to\nhotplug a CPU, we temporarily elevate it's scheduling policy to RT.\nFurthermore, we disallow hotplugging operations to begin if the\ncalling task belongs to the idle and deadline classes or those that\nuse the SCHED_BATCH policy.\n\nChange-Id: Idbb1384626e6ddff46c0d2ce752eee68396c78af\nSigned-off-by: Syed Rameez Mustafa <rameezmustafa@codeaurora.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/16dd35ac488f8e9ef5afa6821ce6e87369c30879"},{"sha":"94f44b64f9c9923f94899560ab38036eb2a43d64","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/fair: Move record_wakee()\n\nSince I want to make ->task_woken() conditional on the task getting\nmigrated, we cannot use it to call record_wakee().\n\nMove it to select_task_rq_fair(), which gets called in almost all the\nsame conditions. The only exception is if the woken task (@p) is\nCPU-bound (as per the nr_cpus_allowed test in select_task_rq()).\n\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Hunter <ahh@google.com>\nCc: Ben Segall <bsegall@google.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Matt Fleming <matt@codeblueprint.co.uk>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Mike Galbraith <umgwanakikbuti@gmail.com>\nCc: Morten Rasmussen <morten.rasmussen@arm.com>\nCc: Paul Turner <pjt@google.com>\nCc: Pavan Kondeti <pkondeti@codeaurora.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: byungchul.park@lge.com\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/94f44b64f9c9923f94899560ab38036eb2a43d64"},{"sha":"fb9e3c72c6e6e337e27fc296daf9c7ca80f09c11","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/fair: Prepare to fix fairness problems on migration\n\nMike reported that our recent attempt to fix migration problems:\n\n  3a47d5124a95 (\"sched/fair: Fix fairness issue on migration\")\n\nbroke interactivity and the signal starve test. We reverted that\ncommit and now let's try it again more carefully, with some other\nunderlying problems fixed first.\n\nOne problem is that I assumed ENQUEUE_WAKING was only set when we do a\ncross-cpu wakeup (migration), which isn't true. This means we now\ndestroy the vruntime history of tasks and wakeup-preemption suffers.\n\nCure this by making my assumption true, only call\nsched_class::task_waking() when we do a cross-cpu wakeup. This avoids\nthe indirect call in the case we do a local wakeup.\n\nReported-by: Mike Galbraith <mgalbraith@suse.de>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Hunter <ahh@google.com>\nCc: Ben Segall <bsegall@google.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Matt Fleming <matt@codeblueprint.co.uk>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Morten Rasmussen <morten.rasmussen@arm.com>\nCc: Paul Turner <pjt@google.com>\nCc: Pavan Kondeti <pkondeti@codeaurora.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: byungchul.park@lge.com\nCc: linux-kernel@vger.kernel.org\nFixes: 3a47d5124a95 (\"sched/fair: Fix fairness issue on migration\")\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/fb9e3c72c6e6e337e27fc296daf9c7ca80f09c11"},{"sha":"d06552587b04af9f87294cb00902a7691a1c82ef","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/core: Kill sched_class::task_waking to clean up the migration logic\n\nWith sched_class::task_waking being called only when we do\nset_task_cpu(), we can make sched_class::migrate_task_rq() do the work\nand eliminate sched_class::task_waking entirely.\n\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Hunter <ahh@google.com>\nCc: Ben Segall <bsegall@google.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Matt Fleming <matt@codeblueprint.co.uk>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Mike Galbraith <umgwanakikbuti@gmail.com>\nCc: Morten Rasmussen <morten.rasmussen@arm.com>\nCc: Paul Turner <pjt@google.com>\nCc: Pavan Kondeti <pkondeti@codeaurora.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: byungchul.park@lge.com\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/d06552587b04af9f87294cb00902a7691a1c82ef"},{"sha":"142a85915a1dc2bc0a833d451cb6859acf6dfbd2","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/fair: Fix fairness issue on migration\n\nPavan reported that in the presence of very light tasks (or cgroups)\nthe placement of migrated tasks can cause severe fairness issues.\n\nThe problem is that enqueue_entity() places the task before it updates\ntime, thereby it can place the task far in the past (remember that\nlight tasks will shoot virtual time forward at a high speed, so in\nrelation to the pre-existing light task, we can land far in the past).\n\nThis is done because update_curr() needs the current task, and we\nmight be placing the current task.\n\nThe obvious solution is to differentiate between the current and any\nother task; placing the current before we update time, and placing any\nother task after, such that !curr tasks end up at the current moment\nin time, and not in the past.\n\nThis commit re-introduces the previously reverted commit:\n\n  3a47d5124a95 (\"sched/fair: Fix fairness issue on migration\")\n\n... which is now safe to do, after we've also fixed another\nunderlying bug first, in:\n\n  sched/fair: Prepare to fix fairness problems on migration\n\nand cleaned up other details in the migration code:\n\n  sched/core: Kill sched_class::task_waking\n\nReported-by: Pavan Kondeti <pkondeti@codeaurora.org>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Mike Galbraith <efault@gmx.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: linux-kernel@vger.kernel.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/142a85915a1dc2bc0a833d451cb6859acf6dfbd2"},{"sha":"087dc5355e4fca095ac06d2a659fa0a574e0bbf0","author":{"name":"Peter Zijlstra","email":"4d3106856cce90e8f40acc5180f60ddda3a23b6e@infradead.org"},"message":"sched/core: Fix remote wakeups\n\nCommit:\n\n  b5179ac70de8 (\"sched/fair: Prepare to fix fairness problems on migration\")\n\n... introduced a bug: Mike Galbraith found that it introduced a\nperformance regression, while Paul E. McKenney reported lost\nwakeups and bisected it to this commit.\n\nThe reason is that I mis-read ttwu_queue() such that I assumed any\nwakeup that got a remote queue must have had the task migrated.\n\nSince this is not so; we need to transfer this information between\nqueueing the wakeup and actually doing the wakeup. Use a new\ntask_struct::sched_flag for this, we already write to\nsched_contributes_to_load in the wakeup path so this is a hot and\nmodified cacheline.\n\nReported-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nReported-by: Mike Galbraith <umgwanakikbuti@gmail.com>\nTested-by: Mike Galbraith <umgwanakikbuti@gmail.com>\nSigned-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>\nCc: Andrew Hunter <ahh@google.com>\nCc: Andy Lutomirski <luto@amacapital.net>\nCc: Ben Segall <bsegall@google.com>\nCc: Borislav Petkov <bp@alien8.de>\nCc: Brian Gerst <brgerst@gmail.com>\nCc: Dave Hansen <dave.hansen@linux.intel.com>\nCc: Denys Vlasenko <dvlasenk@redhat.com>\nCc: Fenghua Yu <fenghua.yu@intel.com>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Matt Fleming <matt@codeblueprint.co.uk>\nCc: Morten Rasmussen <morten.rasmussen@arm.com>\nCc: Oleg Nesterov <oleg@redhat.com>\nCc: Paul Turner <pjt@google.com>\nCc: Pavan Kondeti <pkondeti@codeaurora.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Quentin Casasnovas <quentin.casasnovas@oracle.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: byungchul.park@lge.com\nFixes: b5179ac70de8 (\"sched/fair: Prepare to fix fairness problems on migration\")\nLink: http://lkml.kernel.org/r/20160523091907.GD15728@worktop.ger.corp.intel.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nSigned-off-by: Alex Naidis <alex.naidis@linux.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/087dc5355e4fca095ac06d2a659fa0a574e0bbf0"},{"sha":"0befa094ffbb7c20f9a7ffcf28c6edf1d853f70e","author":{"name":"Tim Murray","email":"1236fbd8e0651a86c12ed0f0b75aaeb5e5852ea8@google.com"},"message":"firmware_class: make firmware caching configurable\n\nBecause firmware caching generates uevent messages that are sent over a\nnetlink socket, it can prevent suspend on many platforms. It's also not\nalways useful, so make it a configurable option.\n\nbug 32180327\n\nChange-Id: I1250512b27edb56caa78d536e5ccf1fb669476ad\nSigned-off-by: Ajay Dudani <adudani@google.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/0befa094ffbb7c20f9a7ffcf28c6edf1d853f70e"},{"sha":"98875ce242d9a736e0a2ac6abbded61d8c737c62","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"qcom-cpufreq: Use CLKFLAG_NO_RATE_CACHE\n\nAfter a CPU comes online, clk_set_rate() silently refuses to change said CPU's\nfrequency to the frequency it was running at before going offline (since it\nthinks that we are setting the same frequency redundantly). By default, each CPU\nruns at its minimum frequency when coming online, so if the governor decides to\nkeep a CPU running at the frequency it used before going offline, then\nclk_set_rate() will ignore the frequency change request and the CPU will stay\nstuck running at its minimum frequency for a potentially long period of time\n(i.e. until the governor decides to change the frequency to something\ndifferent). This can cause severe lag when a device is woken up from deep sleep.\n\nIn order to prevent a CPU from being stuck at its default frequency for a\npotentially long period of time, set the CLKFLAG_NO_RATE_CACHE flag so that the\ngovernor's frequency change requests will always be honored right after a CPU\ncomes online.\n\nNote that this requires a CPU's component clocks to be using CLKFLAG_NO_RATE_CACHE\nas well in order to fix the issue.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/98875ce242d9a736e0a2ac6abbded61d8c737c62"},{"sha":"1b1c2d8231984b69bf0275e52fb5a708889653fa","author":{"name":"Sultanxda","email":"2a26fc11866c4c85a6bb605251817c00bbab3213@gmail.com"},"message":"clk: msm: clock-cpu-8996: Use CLKFLAG_NO_RATE_CACHE for perfcl_hf_mux\n\nThe performance cluster can have frequency change requests ignored when\nit comes online without having this flag set. This can result in the perfcl\nrunning at its default frequency instead of the frequency that the CPU\ngovernor wants.\n\nSigned-off-by: Sultanxda <sultanxda@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/1b1c2d8231984b69bf0275e52fb5a708889653fa"},{"sha":"3132f0ebf7dc323ba5f0d2773d94f07c667009ec","author":{"name":"FedericoBenedetti","email":"3e01b08cf0eb01d8a3a58185c693f15da8a713cc@gmail.com"},"message":"gemini: forgot to delete HZ 300","distinct":true,"url":"https://api.github.com/repos/FedericoBenedetti/android_kernel_xiaomi_msm8996/commits/3132f0ebf7dc323ba5f0d2773d94f07c667009ec"}]}
{"actor":{"display_login":"FedericoBenedetti"}}