{"push_id":543446274,"size":87,"distinct_size":87,"ref":"refs/heads/GE5","head":"2ff3844aaaffe6b9af5f4b3f7c2e55be8ffdc5cf","before":"2ea85952a5d1117a19a4e6900f753c05395c7cd1","commits":[{"sha":"48b634dcfa17794c5e0a49cab886af3e05a49931","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"Revert \"sched: Fix clear NOHZ_BALANCE_KICK\"\n\nThis reverts commit ab5753c4a3c5b9c137468024a4239a726379085d.","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/48b634dcfa17794c5e0a49cab886af3e05a49931"},{"sha":"32a58b365e4afe3d29857c0ee85fd9111db780f4","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"Revert \"msm: idle-v7: flush non secure L1 cache lines for l2 GDHS LPM mode\"\n\nThis reverts commit ceb561d430dc4d26dc80a48fe2bef073d369743b.","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/32a58b365e4afe3d29857c0ee85fd9111db780f4"},{"sha":"445191067574509b3c5a2882b2b0bd363d5cbe4b","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"KEYS: close race between key lookup and freeing\n\nWhen a key is being garbage collected, it's key->user would get put\nbefore\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\nopen\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\nis\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\nlist).\n\nThis would cause either a panic, or corrupt memory.\n\nChange-Id: I01a5ec17916864929458caa9d0fbefea2ca2c5e2\nSigned-off-by: Sasha Levin <sasha.levin@oracle.com>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/445191067574509b3c5a2882b2b0bd363d5cbe4b"},{"sha":"a3bdf47f231fd1f30a7885b6c9ee6f846c8e578a","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"Disable SEC_DEBUG","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/a3bdf47f231fd1f30a7885b6c9ee6f846c8e578a"},{"sha":"9c8b97e306c918de89be90752879fe45617aa071","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"sched: Implement smarter wake-affine logic\n\nThe wake-affine scheduler feature is currently always trying to pull\nthe wakee close to the waker. In theory this should be beneficial if\nthe waker's CPU caches hot data for the wakee, and it's also beneficial\nin the extreme ping-pong high context switch rate case.\n\nTesting shows it can benefit hackbench up to 15%.\n\nHowever, the feature is somewhat blind, from which some workloads\nsuch as pgbench suffer. It's also time-consuming algorithmically.\n\nTesting shows it can damage pgbench up to 50% - far more than the\nbenefit it brings in the best case.\n\nSo wake-affine should be smarter and it should realize when to\nstop its thankless effort at trying to find a suitable CPU to wake on.\n\nThis patch introduces 'wakee_flips', which will be increased each\ntime the task flips (switches) its wakee target.\n\nSo a high 'wakee_flips' value means the task has more than one\nwakee, and the bigger the number, the higher the wakeup frequency.\n\nNow when making the decision on whether to pull or not, pay attention to\nthe wakee with a high 'wakee_flips', pulling such a task may benefit\nthe wakee. Also imply that the waker will face cruel competition later,\nit could be very cruel or very fast depends on the story behind\n'wakee_flips', waker therefore suffers.\n\nFurthermore, if waker also has a high 'wakee_flips', that implies that\nmultiple tasks rely on it, then waker's higher latency will damage all\nof them, so pulling wakee seems to be a bad deal.\n\nThus, when 'waker->wakee_flips / wakee->wakee_flips' becomes\nhigher and higher, the cost of pulling seems to be worse and worse.\n\nThe patch therefore helps the wake-affine feature to stop its pulling\nwork when:\n\n\twakee->wakee_flips > factor &&\n\twaker->wakee_flips > (factor * wakee->wakee_flips)\n\nThe 'factor' here is the number of CPUs in the current CPU's NUMA node,\nso a bigger node will lead to more pulling since the trial becomes more\nsevere.\n\nAfter applying the patch, pgbench shows up to 40% improvements and no\nregressions.\n\nTested with 12 cpu x86 server and tip 3.10.0-rc7.\n\nThe percentages in the final column highlight the areas with the biggest\nwins,\nall other areas improved as well:\n\n\tpgbench\t\t    base\tsmart\n\n\t| db_size | clients |  tps  |\t|  tps  |\n\t+---------+---------+-------+   +-------+\n\t| 22 MB   |       1 | 10598 |   | 10796 |\n\t| 22 MB   |       2 | 21257 |   | 21336 |\n\t| 22 MB   |       4 | 41386 |   | 41622 |\n\t| 22 MB   |       8 | 51253 |   | 57932 |\n\t| 22 MB   |      12 | 48570 |   | 54000 |\n\t| 22 MB   |      16 | 46748 |   | 55982 | +19.75%\n\t| 22 MB   |      24 | 44346 |   | 55847 | +25.93%\n\t| 22 MB   |      32 | 43460 |   | 54614 | +25.66%\n\t| 7484 MB |       1 |  8951 |   |  9193 |\n\t| 7484 MB |       2 | 19233 |   | 19240 |\n\t| 7484 MB |       4 | 37239 |   | 37302 |\n\t| 7484 MB |       8 | 46087 |   | 50018 |\n\t| 7484 MB |      12 | 42054 |   | 48763 |\n\t| 7484 MB |      16 | 40765 |   | 51633 | +26.66%\n\t| 7484 MB |      24 | 37651 |   | 52377 | +39.11%\n\t| 7484 MB |      32 | 37056 |   | 51108 | +37.92%\n\t| 15 GB   |       1 |  8845 |   |  9104 |\n\t| 15 GB   |       2 | 19094 |   | 19162 |\n\t| 15 GB   |       4 | 36979 |   | 36983 |\n\t| 15 GB   |       8 | 46087 |   | 49977 |\n\t| 15 GB   |      12 | 41901 |   | 48591 |\n\t| 15 GB   |      16 | 40147 |   | 50651 | +26.16%\n\t| 15 GB   |      24 | 37250 |   | 52365 | +40.58%\n\t| 15 GB   |      32 | 36470 |   | 50015 | +37.14%\n\nSigned-off-by: Michael Wang <wangyun@linux.vnet.ibm.com>\nCc: Mike Galbraith <efault@gmx.de>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/51D50057.9000809@linux.vnet.ibm.com\n[ Improved the changelog. ]\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/9c8b97e306c918de89be90752879fe45617aa071"},{"sha":"df84f9122fe4d2ba6b52d58f28d4e0fbb6527ccd","author":{"email":"10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","name":"googyanas"},"message":"sched: Micro-optimize the smart wake-affine logic\n\nSmart wake-affine is using node-size as the factor currently, but the\noverhead\nof the mask operation is high.\n\nThus, this patch introduce the 'sd_llc_size' percpu variable, which will\nrecord\nthe highest cache-share domain size, and make it to be the new factor,\nin order\nto reduce the overhead and make it more reasonable.\n\nTested-by: Davidlohr Bueso <davidlohr.bueso@hp.com>\nTested-by: Michael Wang <wangyun@linux.vnet.ibm.com>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nAcked-by: Michael Wang <wangyun@linux.vnet.ibm.com>\nCc: Mike Galbraith <efault@gmx.de>\nLink: http://lkml.kernel.org/r/51D5008E.6030102@linux.vnet.ibm.com\n[ Tidied up the changelog. ]\nSigned-off-by: Ingo Molnar <mingo@kernel.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/df84f9122fe4d2ba6b52d58f28d4e0fbb6527ccd"},{"sha":"793e4ea1efa8d0601e9b046aedf03cac886ba7bc","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"workqueues: Introduce new flag WQ_POWER_EFFICIENT for power oriented workqueues\n\nWorkqueues can be performance or power-oriented. Currently, most workqueues are\nbound to the CPU they were created on. This gives good performance (due to cache\neffects) at the cost of potentially waking up otherwise idle cores (Idle from\nscheduler's perspective. Which may or may not be physically idle) just to\nprocess some work. To save power, we can allow the work to be rescheduled on a\ncore that is already awake.\n\nWorkqueues created with the WQ_UNBOUND flag will allow some power savings.\nHowever, we don't change the default behaviour of the system.  To enable\npower-saving behaviour, a new config option CONFIG_WQ_POWER_EFFICIENT needs to\nbe turned on. This option can also be overridden by the\nworkqueue.power_efficient boot parameter.\n\ntj: Updated config description and comments.  Renamed\n    CONFIG_WQ_POWER_EFFICIENT to CONFIG_WQ_POWER_EFFICIENT_DEFAULT.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nReviewed-by: Amit Kucheria <amit.kucheria@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>\n[zwliew: Backported to msm-3.4]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>\n\nConflicts:\n\tDocumentation/kernel-parameters.txt\n\tinclude/linux/workqueue.h\n\tkernel/power/Kconfig\n\tkernel/workqueue.c","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/793e4ea1efa8d0601e9b046aedf03cac886ba7bc"},{"sha":"1143e82bc005bf16b2bd2cc11edc5f97c1072716","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"workqueue: Add system wide power_efficient workqueues\n\nThis patch adds system wide workqueues aligned towards power saving.\nThis is\ndone by allocating them with WQ_UNBOUND flag if 'wq_power_efficient' is\nset to\n'true'.\n\ntj: updated comments a bit.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>\n\nConflicts:\n\tinclude/linux/workqueue.h\n\tkernel/workqueue.c","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/1143e82bc005bf16b2bd2cc11edc5f97c1072716"},{"sha":"537a9cdded4ade70f032323d8d8f35c5d53743c3","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"Viresh Kumar"},"message":"block: queue work on power efficient wq\n\nBlock layer uses workqueues for multiple purposes. There is no real dependency\nof scheduling these on the cpu which scheduled them.\n\nOn a idle system, it is observed that and idle cpu wakes up many times just to\nservice this work. It would be better if we can schedule it on a cpu which the\nscheduler believes to be the most appropriate one.\n\nThis patch replaces normal workqueues with power efficient versions.\n\nCc: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: Tejun Heo <tj@kernel.org>\n[zwliew: Backport to msm-3.4]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>\n\nConflicts:\n\tblock/genhd.c","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/537a9cdded4ade70f032323d8d8f35c5d53743c3"},{"sha":"b17525b7a1b94f4ea2266dfb81ba222f14b5fead","author":{"email":"6b0d31c0d563223024da45691584643ac78c96e8@bjorling.me","name":"Matias Bjørling"},"message":"block: remove WQ_POWER_EFFICIENT from kblockd\n\nblk-mq issues async requests through kblockd. To issue a work request on\na specific CPU, kblockd_schedule_delayed_work_on is used. However, the\nspecific CPU choice may not be honored, if the power_efficient option\nfor workqueues is set. blk-mq requires that we have strict per-cpu\nscheduling, so it wont work properly if kblockd is marked\nPOWER_EFFICIENT and power_efficient is set.\n\nRemove the kblockd WQ_POWER_EFFICIENT flag to prevent this behavior.\nThis essentially reverts part of commit 695588f9454b, which added\nthe WQ_POWER_EFFICIENT marker to kblockd.\n\nSigned-off-by: Matias Bjørling <m@bjorling.me>\nSigned-off-by: Jens Axboe <axboe@fb.com>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/b17525b7a1b94f4ea2266dfb81ba222f14b5fead"},{"sha":"9cb96abcd46f5e1daeb75a2b9052fa27254e6cd6","author":{"email":"b51b9a92386687a9ac927cebfa0f978adeb8cea5@linaro.org","name":"Mark Brown"},"message":"regulator: core: Use the power efficient workqueue for delayed powerdown\n\nThere is no need to use a normal per-CPU workqueue for delayed power downs\nas they're not timing or performance critical and waking up a core for them\nwould defeat some of the point.\n\nSigned-off-by: Mark Brown <broonie@linaro.org>\nReviewed-by: Viresh Kumar <viresh.kumar@linaro.org>\nAcked-by: Liam Girdwood <liam.r.girdwood@intel.com>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/9cb96abcd46f5e1daeb75a2b9052fa27254e6cd6"},{"sha":"a6f5e59f022ddd21e3da0589b6f6c704f2122ea3","author":{"email":"5ff32272b3d9f86512eddc8e0af523fc6f7924e5@linaro.org","name":"viresh kumar"},"message":"net/neighbour: queue work on power efficient wq\n\nWorkqueue used in neighbour layer have no real dependency of scheduling these on\nthe cpu which scheduled them.\n\nOn a idle system, it is observed that an idle cpu wakes up many times just to\nservice this work. It would be better if we can schedule it on a cpu which the\nscheduler believes to be the most appropriate one.\n\nThis patch replaces normal workqueues with power efficient versions. This\ndoesn't change existing behavior of code unless CONFIG_WQ_POWER_EFFICIENT is\nenabled.\n\nSigned-off-by: Viresh Kumar <viresh.kumar@linaro.org>\nSigned-off-by: David S. Miller <davem@davemloft.net>\n[zwliew: Backport to msm-3.4]\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>\n\nConflicts:\n\tnet/core/neighbour.c","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/a6f5e59f022ddd21e3da0589b6f6c704f2122ea3"},{"sha":"7ab94a3aee999be8e47b42000bec94e47e46fd7b","author":{"email":"f2ad263351ded8bf8d0b90799bb8b9622c429cf8@gmail.com","name":"Zhao Wei Liew"},"message":"workqueue: Include missing header needed for module parameters\n\nSigned-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/7ab94a3aee999be8e47b42000bec94e47e46fd7b"},{"sha":"d97f2c7c9e83263576f3232b2ba83719b7f39d0d","author":{"email":"4c9eb49378914b743bdd32292c04df29b820d73e@cn.fujitsu.com","name":"Lai Jiangshan"},"message":"workqueue: ensure @task is valid across kthread_stop()\n\nWhen a kworker should die, the kworkre is notified through WORKER_DIE\nflag instead of kthread_should_stop().  This, IIRC, is primarily to\nkeep the test synchronized inside worker_pool lock.  WORKER_DIE is\nfirst set while holding pool->lock, the lock is dropped and\nkthread_stop() is called.\n\nUnfortunately, this means that there's a slight chance that the target\nkworker may see WORKER_DIE before kthread_stop() finishes and exits\nand frees the target task before or during kthread_stop().\n\nFix it by pinning the target task before setting WORKER_DIE and\nputting it after kthread_stop() is done.\n\ntj: Improved patch description and comment.  Moved pinning above\n    WORKER_DIE for better signify what it's protecting.\n\nCC: stable@vger.kernel.org\nSigned-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>\nSigned-off-by: Tejun Heo <tj@kernel.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/d97f2c7c9e83263576f3232b2ba83719b7f39d0d"},{"sha":"140766e656482c64aa7b06be5e8ba1b4cee89ed7","author":{"email":"28f0d737c2aab29ec3fb2474afc7fc04c49efb45@codeaurora.org","name":"Subbaraman Narayanamurthy"},"message":"workqueue: fix compilation","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/140766e656482c64aa7b06be5e8ba1b4cee89ed7"},{"sha":"b61fd6e17d8ed27713300b497fdd9f6e947da55e","author":{"email":"d6f051473f553588884d51874952f6fb19ae8261@intel.com","name":"Lin Ming"},"message":"block: add runtime pm helpers\n\nAdd runtime pm helper functions:\n\nvoid blk_pm_runtime_init(struct request_queue *q, struct device *dev)\n  - Initialization function for drivers to call.\n\nint blk_pre_runtime_suspend(struct request_queue *q)\n  - If any requests are in the queue, mark last busy and return -EBUSY.\n    Otherwise set q->rpm_status to RPM_SUSPENDING and return 0.\n\nvoid blk_post_runtime_suspend(struct request_queue *q, int err)\n  - If the suspend succeeded then set q->rpm_status to RPM_SUSPENDED.\n    Otherwise set it to RPM_ACTIVE and mark last busy.\n\nvoid blk_pre_runtime_resume(struct request_queue *q)\n  - Set q->rpm_status to RPM_RESUMING.\n\nvoid blk_post_runtime_resume(struct request_queue *q, int err)\n  - If the resume succeeded then set q->rpm_status to RPM_ACTIVE\n    and call __blk_run_queue, then mark last busy and autosuspend.\n    Otherwise set q->rpm_status to RPM_SUSPENDED.\n\nThe idea and API is designed by Alan Stern and described here:\nhttp://marc.info/?l=linux-scsi&m=133727953625963&w=2\n\nChange-Id: I486612af79c7887116f70a4fde552c107f7fa360\nSigned-off-by: Lin Ming <ming.m.lin@intel.com>\nSigned-off-by: Aaron Lu <aaron.lu@intel.com>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nGit-commit: 6c9546675864f51506af69eca388e5d922942c56\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/b61fd6e17d8ed27713300b497fdd9f6e947da55e"},{"sha":"443cb99a522f57a32e9b36d731c97c7682f5c09c","author":{"email":"d6f051473f553588884d51874952f6fb19ae8261@intel.com","name":"Lin Ming"},"message":"block: implement runtime pm strategy\n\nWhen a request is added:\n    If device is suspended or is suspending and the request is not a\n    PM request, resume the device.\n\nWhen the last request finishes:\n    Call pm_runtime_mark_last_busy().\n\nWhen pick a request:\n    If device is resuming/suspending, then only PM request is allowed\n    to go.\n\nThe idea and API is designed by Alan Stern and described here:\nhttp://marc.info/?l=linux-scsi&m=133727953625963&w=2\n\nChange-Id: If9c8332164afba6aeca984277e3398008ad9c45a\nSigned-off-by: Lin Ming <ming.m.lin@intel.com>\nSigned-off-by: Aaron Lu <aaron.lu@intel.com>\nAcked-by: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nGit-commit: c8158819d506a8aedeca53c52dfb709a0aabe011\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/443cb99a522f57a32e9b36d731c97c7682f5c09c"},{"sha":"8ac49c1ba43196aa91d861b8253a1aaefa4f08f4","author":{"email":"e835aaae27ef45c770cbc83733586d01aadc3a43@intel.com","name":"Aaron Lu"},"message":"blkpm: avoid sleep when holding queue lock\n\nIn blk_post_runtime_resume, an autosuspend request will be initiated for\nthe device. Since we are holding the queue lock, we can't sleep and thus\nwe should use the async version to initiate an autosuspend, i.e.\npm_request_suspend instead of pm_runtime_suspend, which might sleep.\n\nSigned-off-by: Aaron Lu <aaron.lu@intel.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/8ac49c1ba43196aa91d861b8253a1aaefa4f08f4"},{"sha":"8508912f61d391041795a356a5b76ffc194be1bb","author":{"email":"eb7d4bc75c19026be4afbcab4b7b388cf01677ff@linaro.org","name":"Vincent Guittot"},"message":"sched: Fix clear NOHZ_BALANCE_KICK\n\nI have faced a sequence where the Idle Load Balance was sometime not\ntriggered for a while on my platform, in the following scenario:\n\n CPU 0 and CPU 1 are running tasks and CPU 2 is idle\n\n CPU 1 kicks the Idle Load Balance\n CPU 1 selects CPU 2 as the new Idle Load Balancer\n CPU 2 sets NOHZ_BALANCE_KICK for CPU 2\n CPU 2 sends a reschedule IPI to CPU 2\n\n While CPU 3 wakes up, CPU 0 or CPU 1 migrates a waking up task A on CPU 2\n\n CPU 2 finally wakes up, runs task A and discards the Idle Load Balance\n       task A quickly goes back to sleep (before a tick occurs on CPU 2)\n CPU 2 goes back to idle with NOHZ_BALANCE_KICK set\n\nWhenever CPU 2 will be selected as the ILB, no reschedule IPI will be sent\nbecause NOHZ_BALANCE_KICK is already set and no Idle Load Balance will be\nperformed.\n\nWe must wait for the sched softirq to be raised on CPU 2 thanks to another\npart the kernel to come back to clear NOHZ_BALANCE_KICK.\n\nThe proposed solution clears NOHZ_BALANCE_KICK in schedule_ipi if\nwe can't raise the sched_softirq for the Idle Load Balance.\n\nChange since V1:\n\n- move the clear of NOHZ_BALANCE_KICK in got_nohz_idle_kick if the ILB\n  can't run on this CPU (as suggested by Peter)\n\nSigned-off-by: Vincent Guittot <vincent.guittot@linaro.org>\nSigned-off-by: Peter Zijlstra <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1370419991-13870-1-git-send-email-vincent.guittot@linaro.org\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\nGit-commit: 873b4c65b519fd769940eb281f77848227d4e5c1\nGit-repo: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git\n[smuckle@codeaurora.org: minor merge resolution for 3.4 in scheduler_ipi()]\nSigned-off-by: Steve Muckle <smuckle@codeaurora.org>\nChange-Id: I3548612057cccc2ecc29429c129c44183083831f","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/8508912f61d391041795a356a5b76ffc194be1bb"},{"sha":"c5d85ad65c52d9ab48bcd35f80cd547357351475","author":{"email":"a781eab460d0b8de6413720f3ae4346867408d60@codeaurora.org","name":"Alok Chauhan"},"message":"msm: msm_bus: Fix the type error causing bandwidth overflow\n\nOn legacy chipsets, long int was being used to store\nreturn value after calculating interleaved bw. However,\nNoCs support 64-bit integers ab/ib values. problme occurs\nif client request for higher bw and if difference of ab\nvalue exceeds the range of 32 bit integer, the Value\noverflows and turns negative, which leads to wrong bw calculation.\n\nThis patch fixes this integer overflow by correcting argument\ntype to store bw.\n\nCRs-Fixed: 537213\nChange-Id: I8c6c79ba245a988c2c54ccaca3f3eaf5cb857ce5\nSigned-off-by: Alok Chauhan <alokc@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/googyanas/Googy-Max3-Kernel/commits/c5d85ad65c52d9ab48bcd35f80cd547357351475"}]}