{"push_id":669235396,"size":7,"distinct_size":7,"ref":"refs/heads/lp-test","head":"fd0a65af6ef1d270cf9a5f379aaea9b579c4d003","before":"63e362cdd5cc2c733a824aa0036b5c7b05afd25e","commits":[{"sha":"c2ea8a5683f19dc09ea8e2f6ade0db01319d7b9b","author":{"email":"d32984257c2b1f19a52887b31db69164a662fd03@codeaurora.org","name":"Anji Jonnala"},"message":"arch: arm: TLB invalidate if power collapse gets aborted\n\nInvalidate entire local TLB in non sharable mode when\npower collapse is aborted due to pending interrupt.\n\nChange-Id: Ie6d46db8f6c1779b4f15e8940ad961a4cd014e37\nSigned-off-by: Anji Jonnala <anjir@codeaurora.org>\nSigned-off-by: Venkat Devarasetty <vdevaras@codeaurora.org>","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/c2ea8a5683f19dc09ea8e2f6ade0db01319d7b9b"},{"sha":"7d7331ac55ab334ebb30153a1a08ad3ce9a6cac0","author":{"email":"45d857216ef082c1ddfd5d3991b4f3d23f51761f@arcor.de","name":"myfluxi"},"message":"block: deadline: Optimize for non-rotational","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/7d7331ac55ab334ebb30153a1a08ad3ce9a6cac0"},{"sha":"35f3f3f4aeb2a25a69b372f01014dcb365c4e2cd","author":{"email":"16eb3ae3aa3fc30066a5ca11bf4d56728b480a7d@qq.com","name":"shminer"},"message":"block:fiops miss","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/35f3f3f4aeb2a25a69b372f01014dcb365c4e2cd"},{"sha":"8bf87bca028d9dde0d7222bb878cc6a32c5a002b","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"mm: vmpressure: allow in-kernel clients to subscribe for events\n\nCurrently, vmpressure is tied to memcg and its events are\navailable only to userspace clients. This patch removes\nthe dependency on CONFIG_MEMCG and adds a mechanism for\nin-kernel clients to subscribe for vmpressure events (in\nfact raw vmpressure values are delivered instead of vmpressure\nlevels, to provide clients more flexibility to take actions\non custom pressure levels which are not currently defined\nby vmpressure module).\n\nChange-Id: I38010f166546e8d7f12f5f355b5dbfd6ba04d587\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\n\nConflicts:\n\tmm/Makefile","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/8bf87bca028d9dde0d7222bb878cc6a32c5a002b"},{"sha":"a6ef325884b9839f63da204e3745d75f7e45526f","author":{"email":"db18ceb40708dab5e9bcdbeb620f7eed18da08e5@codeaurora.org","name":"Vinayak Menon"},"message":"mm: vmpressure: scale pressure based on reclaim context\n\nThe existing calculation of vmpressure takes into account only\nthe ratio of reclaimed to scanned pages, but not the time spent\nor the difficulty in reclaiming those pages. For e.g. when there\nare quite a number of file pages in the system, an allocation\nrequest can be satisfied by reclaiming the file pages alone. If\nsuch a reclaim is succesful, the vmpressure value will remain low\nirrespective of the time spent by the reclaim code to free up the\nfile pages. With a feature like lowmemorykiller, killing a task\ncan be faster than reclaiming the file pages alone. So if the\nvmpressure values reflect the reclaim difficulty level, clients\ncan make a decision based on that, for e.g. to kill a task early.\n\nThis patch monitors the number of pages scanned in the direct\nreclaim path and scales the vmpressure level according to that.\n\nSigned-off-by: Vinayak Menon <vinmenon@codeaurora.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/a6ef325884b9839f63da204e3745d75f7e45526f"},{"sha":"e0c77c9ecb84da158246d7d857407c2008de8bcf","author":{"email":"69652caca27c8b940640ad396ab71f93cacec34f@linux-foundation.org","name":"Linus Torvalds"},"message":"mm: don't pointlessly use BUG_ON() for sanity check\n\nBUG_ON() is a big hammer, and should be used _only_ if there is some\nmajor corruption that you cannot possibly recover from, making it\nimperative that the current process (and possibly the whole machine) be\nterminated with extreme prejudice.\n\nThe trivial sanity check in the vmacache code is *not* such a fatal\nerror.  Recovering from it is absolutely trivial, and using BUG_ON()\njust makes it harder to debug for no actual advantage.\n\nTo make matters worse, the placement of the BUG_ON() (only if the range\ncheck matched) actually makes it harder to hit the sanity check to begin\nwith, so _if_ there is a bug (and we just got a report from Srivatsa\nBhat that this can indeed trigger), it is harder to debug not just\nbecause the machine is possibly dead, but because we don't have better\ncoverage.\n\nBUG_ON() must *die*.  Maybe we should add a checkpatch warning for it,\nbecause it is simply just about the worst thing you can ever do if you\nhit some \"this cannot happen\" situation.\n\nReported-by: Srivatsa S. Bhat <srivatsa.bhat@linux.vnet.ibm.com>\nCc: Davidlohr Bueso <davidlohr@hp.com>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/e0c77c9ecb84da158246d7d857407c2008de8bcf"},{"sha":"fd0a65af6ef1d270cf9a5f379aaea9b579c4d003","author":{"email":"4aa5652442886f3c4e77d3a743dc27e129c1613f@hp.com","name":"Davidlohr Bueso"},"message":"mm,vmacache: optimize overflow system-wide flushing\n\nFor single threaded workloads, we can avoid flushing and iterating through\nthe entire list of tasks, making the whole function a lot faster,\nrequiring only a single atomic read for the mm_users.\n\nSigned-off-by: Davidlohr Bueso <davidlohr@hp.com>\nSuggested-by: Oleg Nesterov <oleg@redhat.com>\nCc: Aswin Chandramouleeswaran <aswin@hp.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","distinct":true,"url":"https://api.github.com/repos/shminer/LG-F460-Kernel/commits/fd0a65af6ef1d270cf9a5f379aaea9b579c4d003"}]}