{"push_id":973635285,"size":31,"distinct_size":31,"ref":"refs/heads/reborn3","head":"aee23419e42323f90cd9860517790d16b445742f","before":"c3ce5fd43ae4e5963a549cd34729544a4c31f72d","commits":[{"sha":"5943979a4a792452bd829103b8c2db91056d4f5a","author":{"email":"749e12e18869a210449c40d360fd34eba62d827d@gmail.com","name":"Jorge Ayres Pereira"},"message":"bcmdhd: reduce to 250ms\n\nSigned-off-by: YoshiShaPow <yoshipga@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/5943979a4a792452bd829103b8c2db91056d4f5a"},{"sha":"13ba3c84fb5ce2f75ca3417db59eacd4fc8f1fd8","author":{"email":"749e12e18869a210449c40d360fd34eba62d827d@gmail.com","name":"Jorge Ayres Pereira"},"message":"Enable UNALIGNED_ACCESS, this will actually improve kernel performance.","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/13ba3c84fb5ce2f75ca3417db59eacd4fc8f1fd8"},{"sha":"9d20263c161ee6054e2786dead8468a984067906","author":{"email":"ae947f3c8df96e1dc851c5e3e5a930ce6d3f1f74@windriver.com","name":"Paul Gortmaker"},"message":"PM / tracing: remove deprecated power trace API\n\nThe text in Documentation said it would be removed in 2.6.41;\nthe text in the Kconfig said removal in the 3.1 release.  Either\nway you look at it, we are well past both, so push it off a cliff.\n\nNote that the POWER_CSTATE and the POWER_PSTATE are part of the\nlegacy tracing API.  Remove all tracepoints which use these flags.\nAs can be seen from context, most already have a trace entry via\ntrace_cpu_idle anyways.\n\nAlso, the cpufreq/cpufreq.c PSTATE one is actually unpaired, as\ncompared to the CSTATE ones which all have a clear start/stop.\nAs part of this, the trace_power_frequency also becomes orphaned,\nso it too is deleted.\n\nSigned-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>\nAcked-by: Steven Rostedt <rostedt@goodmis.org>\nSigned-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tkernel/trace/Kconfig\n\nConflicts:\n\tdrivers/cpuidle/cpuidle.c","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/9d20263c161ee6054e2786dead8468a984067906"},{"sha":"6b9b2ffc7ab1fb10300e49558a178571bec54f4c","author":{"email":"749e12e18869a210449c40d360fd34eba62d827d@gmail.com","name":"jgcaap"},"message":"NFC: reduce frequency to 19.2MHz\n\nSigned-off-by: YoshiShaPow <yoshipga@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/6b9b2ffc7ab1fb10300e49558a178571bec54f4c"},{"sha":"e1a88c5ef9a957af3b3d550e594212ff7a7a275d","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"msm: bam_dmux: Reduce debug logs to avoid watchdog bite\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/e1a88c5ef9a957af3b3d550e594212ff7a7a275d"},{"sha":"c3555b96e5b2f56fa358fcad5045efc23f55c4a6","author":{"email":"d688953a19dcb476c5fb90e6abba87f77b09be65@gmail.com","name":"Pranav Vashi"},"message":"msm: bam_dmux: Tune values and remove panic\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tarch/arm/mach-msm/bam_dmux.c","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/c3555b96e5b2f56fa358fcad5045efc23f55c4a6"},{"sha":"54e6545f32de072b07af070668a6ab88ad7cc1fc","author":{"email":"5b4d8dc9ea337fff5fd1729321eda9873ade0b09@ti.com","name":"Santosh Shilimkar"},"message":"ARM: 7674/1: smp: Avoid dummy clockevent being preferred over real hardware clock-event\n\nWith recent arm broadcast time clean-up from Mark Rutland, the dummy\nbroadcast device is always registered with timer subsystem. And since\nthe rating of the dummy clock event is very high, it may be preferred\nover a real clock event.\n\nThis is a change in behavior from past and not an intended one. So\nreduce the rating of the dummy clock-event so that real clock-event\ndevice is selected when available.\n\nAcked-by: Thomas Gleixner <tglx@linutronix.de>\nAcked-by: Mark Rutland <mark.rutland@arm.com>\nSigned-off-by: Santosh Shilimkar <santosh.shilimkar@ti.com>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/54e6545f32de072b07af070668a6ab88ad7cc1fc"},{"sha":"0202da10654f972b4e2c67b77fed71d17bce5a13","author":{"email":"66d3c5fdaeea7ff1f996ad04f2c45e08ab38e2f5@linaro.org","name":"Ard Biesheuvel"},"message":"crypto: arm/aes update NEON AES module to latest OpenSSL version\n\nThis updates the bit sliced AES module to the latest version in the\nupstream OpenSSL repository (e620e5ae37bc). This is needed to fix a\nbug in the XTS decryption path, where data chunked in a certain way\ncould trigger the ciphertext stealing code, which is not supposed to\nbe active in the kernel build (The kernel implementation of XTS only\nsupports round multiples of the AES block size of 16 bytes, whereas\nthe conformant OpenSSL implementation of XTS supports inputs of\narbitrary size by applying ciphertext stealing). This is fixed in\nthe upstream version by adding the missing #ifndef XTS_CHAIN_TWEAK\naround the offending instructions.\n\nThe upstream code also contains the change applied by Russell to\nbuild the code unconditionally, i.e., even if __LINUX_ARM_ARCH__ < 7,\nbut implemented slightly differently.\n\nCc: stable@vger.kernel.org\nFixes: e4e7f10bfc40 (\"ARM: add support for bit sliced AES using NEON instructions\")\nReported-by: Adrian Kotelba <adrian.kotelba@gmail.com>\nSigned-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>\nTested-by: Milan Broz <gmazyland@gmail.com>\nSigned-off-by: Herbert Xu <herbert@gondor.apana.org.au>\n\nChange-Id: I8973ae15cb082993c954b573bef9baa7195157e7","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/0202da10654f972b4e2c67b77fed71d17bce5a13"},{"sha":"a774e6d71241ea8d3c1485250ec9cfa578f93f9f","author":{"email":"c208d1ecece4e5ef2e4fb72f0546c69cdce89063@gmail.com","name":"Paul Reioux"},"message":"msm8974-regulator.dtsi: further reduce CPU retention voltage\n\nthis should help idel drain during processor retention c-state\n\nSigned-off-by: Paul Reioux <reioux@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/a774e6d71241ea8d3c1485250ec9cfa578f93f9f"},{"sha":"4f1f16605d313e70106a039b88569de9591fc09c","author":{"email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","name":"Thomas Gleixner"},"message":"irq: Ensure irq_exit() code runs with interrupts disabled\n\nWe had already a few problems with code called from irq_exit() when\ninterrupted from a nesting interrupt. This can happen on architectures\nwhich do not define __ARCH_IRQ_EXIT_IRQS_DISABLED.\n\n__ARCH_IRQ_EXIT_IRQS_DISABLED should go away and we want to make it\nmandatory to call irq_exit() with interrupts disabled.\n\nAs a temporary protection disable interrupts for those architectures\nwhich do not define __ARCH_IRQ_EXIT_IRQS_DISABLED and add a WARN_ONCE\nwhen an architecture which defines __ARCH_IRQ_EXIT_IRQS_DISABLED calls\nirq_exit() with interrupts enabled.\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/4f1f16605d313e70106a039b88569de9591fc09c"},{"sha":"6339ecd78762363fd41533165186dab7604cd7ef","author":{"email":"00e4cf8f46a57000a44449bf9dd8cbbcc209fd2a@linutronix.de","name":"Thomas Gleixner"},"message":"irq: Sanitize invoke_softirq\n\nWith the irq protection in irq_exit, we can remove the #ifdeffery and\nthe bh_disable/enable dance in invoke_softirq()\n\nSigned-off-by: Thomas Gleixner <tglx@linutronix.de>\nCc: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nCc: Linus Torvalds <torvalds@linuxfoundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/6339ecd78762363fd41533165186dab7604cd7ef"},{"sha":"f390c0806eb75e6b3c38ea364cfbf6f05e06a9b4","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Remove IRQ_EXIT_OFFSET workaround\n\nThe IRQ_EXIT_OFFSET trick was used to make sure the irq\ndoesn't get preempted after we substract the HARDIRQ_OFFSET\nuntil we are entirely done with any code in irq_exit().\n\nThis workaround was necessary because some archs may call\nirq_exit() with irqs enabled and there is still some code\nin the end of this function that is not covered by the\nHARDIRQ_OFFSET but want to stay non-preemptible.\n\nNow that irq are always disabled in irq_exit(), the whole code\nis guaranteed not to be preempted. We can thus remove this hack.\n\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/f390c0806eb75e6b3c38ea364cfbf6f05e06a9b4"},{"sha":"0333e38f6e222b1149109a12cb77f6cf4bfd9215","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Don't re-enable interrupts at the end of irq_exit\n\nCommit \"irq: Ensure irq_exit() code runs with interrupts disabled\"\nrestore interrupts flags in the end of irq_exit() for archs\nthat don't define __ARCH_IRQ_EXIT_IRQS_DISABLED.\n\nHowever always returning from irq_exit() with interrupts\ndisabled should not be a problem for these archs. Prior to\nthis commit this was already happening anytime we processed\npending softirqs anyway.\n\nSuggested-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Paul E. McKenney <paulmck@linux.vnet.ibm.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/0333e38f6e222b1149109a12cb77f6cf4bfd9215"},{"sha":"df130b347c73d9a9d8dc7d054ed032ac9760939f","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Force hardirq exit's softirq processing on its own stack\n\nThe commit facd8b80c67a3cf64a467c4a2ac5fb31f2e6745b\n(\"irq: Sanitize invoke_softirq\") converted irq exit\ncalls of do_softirq() to __do_softirq() on all architectures,\nassuming it was only used there for its irq disablement\nproperties.\n\nBut as a side effect, the softirqs processed in the end\nof the hardirq are always called on the inline current\nstack that is used by irq_exit() instead of the softirq\nstack provided by the archs that override do_softirq().\n\nThe result is mostly safe if the architecture runs irq_exit()\non a separate irq stack because then softirqs are processed\non that same stack that is near empty at this stage (assuming\nhardirq aren't nesting).\n\nOtherwise irq_exit() runs in the task stack and so does the softirq\ntoo. The interrupted call stack can be randomly deep already and\nthe softirq can dig through it even further. To add insult to the\ninjury, this softirq can be interrupted by a new hardirq, maximizing\nthe chances for a stack overrun as reported in powerpc for example:\n\n\tdo_IRQ: stack overflow: 1920\n\tCPU: 0 PID: 1602 Comm: qemu-system-ppc Not tainted 3.10.4-300.1.fc19.ppc64p7 #1\n\tCall Trace:\n\t[c0000000050a8740] .show_stack+0x130/0x200 (unreliable)\n\t[c0000000050a8810] .dump_stack+0x28/0x3c\n\t[c0000000050a8880] .do_IRQ+0x2b8/0x2c0\n\t[c0000000050a8930] hardware_interrupt_common+0x154/0x180\n\t--- Exception: 501 at .cp_start_xmit+0x3a4/0x820 [8139cp]\n\t\tLR = .cp_start_xmit+0x390/0x820 [8139cp]\n\t[c0000000050a8d40] .dev_hard_start_xmit+0x394/0x640\n\t[c0000000050a8e00] .sch_direct_xmit+0x110/0x260\n\t[c0000000050a8ea0] .dev_queue_xmit+0x260/0x630\n\t[c0000000050a8f40] .br_dev_queue_push_xmit+0xc4/0x130 [bridge]\n\t[c0000000050a8fc0] .br_dev_xmit+0x198/0x270 [bridge]\n\t[c0000000050a9070] .dev_hard_start_xmit+0x394/0x640\n\t[c0000000050a9130] .dev_queue_xmit+0x428/0x630\n\t[c0000000050a91d0] .ip_finish_output+0x2a4/0x550\n\t[c0000000050a9290] .ip_local_out+0x50/0x70\n\t[c0000000050a9310] .ip_queue_xmit+0x148/0x420\n\t[c0000000050a93b0] .tcp_transmit_skb+0x4e4/0xaf0\n\t[c0000000050a94a0] .__tcp_ack_snd_check+0x7c/0xf0\n\t[c0000000050a9520] .tcp_rcv_established+0x1e8/0x930\n\t[c0000000050a95f0] .tcp_v4_do_rcv+0x21c/0x570\n\t[c0000000050a96c0] .tcp_v4_rcv+0x734/0x930\n\t[c0000000050a97a0] .ip_local_deliver_finish+0x184/0x360\n\t[c0000000050a9840] .ip_rcv_finish+0x148/0x400\n\t[c0000000050a98d0] .__netif_receive_skb_core+0x4f8/0xb00\n\t[c0000000050a99d0] .netif_receive_skb+0x44/0x110\n\t[c0000000050a9a70] .br_handle_frame_finish+0x2bc/0x3f0 [bridge]\n\t[c0000000050a9b20] .br_nf_pre_routing_finish+0x2ac/0x420 [bridge]\n\t[c0000000050a9bd0] .br_nf_pre_routing+0x4dc/0x7d0 [bridge]\n\t[c0000000050a9c70] .nf_iterate+0x114/0x130\n\t[c0000000050a9d30] .nf_hook_slow+0xb4/0x1e0\n\t[c0000000050a9e00] .br_handle_frame+0x290/0x330 [bridge]\n\t[c0000000050a9ea0] .__netif_receive_skb_core+0x34c/0xb00\n\t[c0000000050a9fa0] .netif_receive_skb+0x44/0x110\n\t[c0000000050aa040] .napi_gro_receive+0xe8/0x120\n\t[c0000000050aa0c0] .cp_rx_poll+0x31c/0x590 [8139cp]\n\t[c0000000050aa1d0] .net_rx_action+0x1dc/0x310\n\t[c0000000050aa2b0] .__do_softirq+0x158/0x330\n\t[c0000000050aa3b0] .irq_exit+0xc8/0x110\n\t[c0000000050aa430] .do_IRQ+0xdc/0x2c0\n\t[c0000000050aa4e0] hardware_interrupt_common+0x154/0x180\n\t --- Exception: 501 at .bad_range+0x1c/0x110\n\t\t LR = .get_page_from_freelist+0x908/0xbb0\n\t[c0000000050aa7d0] .list_del+0x18/0x50 (unreliable)\n\t[c0000000050aa850] .get_page_from_freelist+0x908/0xbb0\n\t[c0000000050aa9e0] .__alloc_pages_nodemask+0x21c/0xae0\n\t[c0000000050aaba0] .alloc_pages_vma+0xd0/0x210\n\t[c0000000050aac60] .handle_pte_fault+0x814/0xb70\n\t[c0000000050aad50] .__get_user_pages+0x1a4/0x640\n\t[c0000000050aae60] .get_user_pages_fast+0xec/0x160\n\t[c0000000050aaf10] .__gfn_to_pfn_memslot+0x3b0/0x430 [kvm]\n\t[c0000000050aafd0] .kvmppc_gfn_to_pfn+0x64/0x130 [kvm]\n\t[c0000000050ab070] .kvmppc_mmu_map_page+0x94/0x530 [kvm]\n\t[c0000000050ab190] .kvmppc_handle_pagefault+0x174/0x610 [kvm]\n\t[c0000000050ab270] .kvmppc_handle_exit_pr+0x464/0x9b0 [kvm]\n\t[c0000000050ab320]  kvm_start_lightweight+0x1ec/0x1fc [kvm]\n\t[c0000000050ab4f0] .kvmppc_vcpu_run_pr+0x168/0x3b0 [kvm]\n\t[c0000000050ab9c0] .kvmppc_vcpu_run+0xc8/0xf0 [kvm]\n\t[c0000000050aba50] .kvm_arch_vcpu_ioctl_run+0x5c/0x1a0 [kvm]\n\t[c0000000050abae0] .kvm_vcpu_ioctl+0x478/0x730 [kvm]\n\t[c0000000050abc90] .do_vfs_ioctl+0x4ec/0x7c0\n\t[c0000000050abd80] .SyS_ioctl+0xd4/0xf0\n\t[c0000000050abe30] syscall_exit+0x0/0x98\n\nSince this is a regression, this patch proposes a minimalistic\nand low-risk solution by blindly forcing the hardirq exit processing of\nsoftirqs on the softirq stack. This way we should reduce significantly\nthe opportunities for task stack overflow dug by softirqs.\n\nLonger term solutions may involve extending the hardirq stack coverage to\nirq_exit(), etc...\n\nReported-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: #3.9.. <stable@vger.kernel.org>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/df130b347c73d9a9d8dc7d054ed032ac9760939f"},{"sha":"f7b802ced2ed749bf2cd8df2e6d71c3ddfb481ba","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Consolidate do_softirq() arch overriden implementations\n\nAll arch overriden implementations of do_softirq() share the following\ncommon code: disable irqs (to avoid races with the pending check),\ncheck if there are softirqs pending, then execute __do_softirq() on\na specific stack.\n\nConsolidate the common parts such that archs only worry about the\nstack switch.\n\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/f7b802ced2ed749bf2cd8df2e6d71c3ddfb481ba"},{"sha":"affaeb505944cf810eff043f650f4a137837eac6","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Optimize call to softirq on hardirq exit\n\nBefore processing softirqs on hardirq exit, we already\ndo the check for pending softirqs while hardirqs are\nguaranteed to be disabled.\n\nSo we can take a shortcut and safely jump to the arch\nspecific implementation directly.\n\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/affaeb505944cf810eff043f650f4a137837eac6"},{"sha":"680c2c4ec31e05db70c0ef319bb8c0d79610b177","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Improve a bit softirq debugging\n\ndo_softirq() has a debug check that verifies that it is not nesting\non softirqs processing, nor miscounting the softirq part of the preempt\ncount.\n\nBut making sure that softirqs processing don't nest is actually a more\ngeneric concern that applies to any caller of __do_softirq().\n\nDo take it one step further and generalize that debug check to\nany softirq processing.\n\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/680c2c4ec31e05db70c0ef319bb8c0d79610b177"},{"sha":"4729b558ab8b79356ef6595d69b81a017ce44064","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Justify the various softirq stack choices\n\nFor clarity, comment the various stack choices for softirqs\nprocessing, whether we execute them from ksoftirqd or\nlocal_irq_enable() calls.\n\nTheir use on irq_exit() is already commented.\n\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/4729b558ab8b79356ef6595d69b81a017ce44064"},{"sha":"eb19d9253b008b83ac7037a7c5a82c439c3db55c","author":{"email":"e8a1bf9163cb25e93cfd6540f223b3872ea7ee55@gmail.com","name":"Frederic Weisbecker"},"message":"irq: Optimize softirq stack selection in irq exit\n\nIf irq_exit() is called on the arch's specified irq stack,\nit should be safe to run softirqs inline under that same\nirq stack as it is near empty by the time we call irq_exit().\n\nFor example if we use the same stack for both hard and soft irqs here,\nthe worst case scenario is:\nhardirq -> softirq -> hardirq. But then the softirq supersedes the\nfirst hardirq as the stack user since irq_exit() is called in\na mostly empty stack. So the stack merge in this case looks acceptable.\n\nStack overrun still have a chance to happen if hardirqs have more\nopportunities to nest, but then it's another problem to solve.\n\nSo lets adapt the irq exit's softirq stack on top of a new Kconfig symbol\nthat can be defined when irq_exit() runs on the irq stack. That way\nwe can spare some stack switch on irq processing and all the cache\nissues that come along.\n\nAcked-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Frederic Weisbecker <fweisbec@gmail.com>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: Ingo Molnar <mingo@kernel.org>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: H. Peter Anvin <hpa@zytor.com>\nCc: Linus Torvalds <torvalds@linux-foundation.org>\nCc: Paul Mackerras <paulus@au1.ibm.com>\nCc: James Hogan <james.hogan@imgtec.com>\nCc: James E.J. Bottomley <jejb@parisc-linux.org>\nCc: Helge Deller <deller@gmx.de>\nCc: Martin Schwidefsky <schwidefsky@de.ibm.com>\nCc: Heiko Carstens <heiko.carstens@de.ibm.com>\nCc: David S. Miller <davem@davemloft.net>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\n\nConflicts:\n\tarch/Kconfig\n\nConflicts:\n\tarch/Kconfig","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/eb19d9253b008b83ac7037a7c5a82c439c3db55c"},{"sha":"907fc489ab7000101a865eb97ce963eeba8d9dd1","author":{"email":"9be92b3dbbd6611e3e4c9209fb3d04b4919e7cca@citrix.com","name":"Ian Campbell"},"message":"ARM: 7824/1: update advice on kernel, initramfs and FDT load address.\n\n  - Recommend that the kernel be placed under 128MiB, this is required if\n    CONFIG_AUTO_ZRELADDR=y and good (or at least not bad) advice even if\n    CONFIG_AUTO_ZRELADDR=n.\n  - Recommend that a zImage kernel be placed above 32MiB, this avoids the need\n    to relocate prior to decompression, which can speed up boot.\n  - Add basic info on the requirements when loading a raw (non-zImage) kernel\n    which are stricter than the zImage requirements.\n  - Recommend that the DTB be placed after the 128MiB boundary, avoiding any\n    potential conflict with the kernel decompressor, and within the lowmem\n    region.  In practice it could follow the kernel loaded after 32MiB,\n    assuming the kernel decompesses to less than 32MiB, but the 128MiB\n    recommendation is simple and unambiguous.\n  - Add similar recommendation regarding initramfs.\n\nSigned-off-by: Ian Campbell <ian.campbell@citrix.com>\nCc: Nicolas Pitre <nicolas.pitre@linaro.org>\nCc: Will Deacon <will.deacon@arm.com>\nCc: Dave Martin <dave.martin@linaro.org>\nCc: Grant Likely <grant.likely@secretlab.ca>\nCc: Roy Franz <roy.franz@linaro.org>\nCc: linux-arm-kernel@lists.infradead.org\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/acuicultor/android_kernel_oneplus_msm8974/commits/907fc489ab7000101a865eb97ce963eeba8d9dd1"}]}