{"push_id":848378145,"size":29,"distinct_size":29,"ref":"refs/heads/test","head":"413f1e4cc8408a32e4940f0ab2616d66fbceb39c","before":"6d969995c752ac059d9f3b90c8c332b9162e495f","commits":[{"sha":"40106c11a9496da621a4625f7c448446add84cef","author":{"email":"672c7f5d7c31e5aba75fbe0bc303fff4514dcd5f@gmail.com","name":"morfic"},"message":"Mako (absolute) Voltage control.\n\nThis started out as just including the existing work of someone else.\nBut that was so obfuscated and needlessly moved in sysfs, i turned it into the type control\nwe have on NP, meaning same sysfs location and output formatting.\nSince the various kernels range from no preUV to different levels of UV it is best to encourage the user\nto think in absolute voltages.\n\"I can UV -150 on kernel X! Really? Odd, i can only UV kernel Y -50mV!\"\nKernel X has no preUV, kernel Y has 100mV preUV, so they both run the same.\nThis is needlessly confusing to users.\n\nTalking in absolutes, users will get a better understanding of \"what the other guy's\" device is capable of.\nSticking to a common sysfs location and to the common absolute voltage is thus the right thing to do.\n\nThis seems to work now as it should.\n\nThis is heavily based on coolbho3k's NP patch. from Paul's mess we might have a few function names, but not the contents.\nThis is not his, if he claims otherwise, he can go fuck himself.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: clean it up, make it elegant and remove the constrain of fixed set of NUM_FREQS - its not dynamic based on the number of freqs used for scaling via an external function.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: few minor changes, mostly for clarity.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nUndervolt: add checks to disallow too extreme voltages, min and max.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nmsm: fix indendation and improve the routines.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/40106c11a9496da621a4625f7c448446add84cef"},{"sha":"f060a255129228a5c32df8f7a2f25c0b37aa7f8c","author":{"email":"d09719b174b1d7232763de9bbeaca66508591b55@codeaurora.org","name":"Sujit Reddy Thumma"},"message":"cfq-iosched: Fix null pointer dereference\n\nNULL pointer dereference can happen in cfq_choose_cfqg()\nwhen there are no cfq groups to select other than the\ncurrent serving group. Prevent this by adding a NULL\ncheck before dereferencing.\n\nUnable to handle kernel NULL pointer dereference at virtual address\n[<c02502cc>] (cfq_dispatch_requests+0x368/0x8c0) from\n[<c0243f30>] (blk_peek_request+0x220/0x25c)\n[<c0243f30>] (blk_peek_request+0x220/0x25c) from\n[<c0243f74>] (blk_fetch_request+0x8/0x1c)\n[<c0243f74>] (blk_fetch_request+0x8/0x1c) from\n[<c041cedc>] (mmc_queue_thread+0x58/0x120)\n[<c041cedc>] (mmc_queue_thread+0x58/0x120) from\n[<c00ad310>] (kthread+0x84/0x90)\n[<c00ad310>] (kthread+0x84/0x90) from\n[<c000eeac>] (kernel_thread_exit+0x0/0x8)\n\nCRs-Fixed: 416466\nChange-Id: I1fab93a4334b53e1d7c5dcc8f93cff174bae0d5e\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/f060a255129228a5c32df8f7a2f25c0b37aa7f8c"},{"sha":"02d36bef44df2bbc3094234b1e07f64a271a904f","author":{"email":"b2a0efa288d2011c6587a4a8516b5d7bd5f3174b@intel.com","name":"xiaobing tu"},"message":"deadline: Allow 0ms deadline latency, increase the read speed\n\nChange a timer compare from after to after-equals, thus allowing\n0 timeout and making deadline schedule FIFO.\n\nSigned-off-by: xiaobing tu <xiaobing.tu@intel.com>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/02d36bef44df2bbc3094234b1e07f64a271a904f"},{"sha":"8f916965b6c725b44cd8aafb04dc491ff9acc22f","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"Francisco Franco"},"message":"mako: display: fix RGB values to be reset each screen on/off.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/8f916965b6c725b44cd8aafb04dc491ff9acc22f"},{"sha":"fde3c35c7938daa10c4e4f10dea0d8901b7d362e","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"Francisco Franco"},"message":"mako: gamma_adjustments: add extensive control over the display gamma curve.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\ngamma_control: fix permissions for userspace apps.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\ngamma_control: change to stock values.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nConflicts:\n\tdrivers/misc/Kconfig\n\tdrivers/misc/Makefile","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/fde3c35c7938daa10c4e4f10dea0d8901b7d362e"},{"sha":"9456a0ff5906cd2fcba41c731fb29dc99379df0c","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"Added fsync on/off support.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nfs: sync: enable fsync by default.\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>\n\nfs: sync: add missing return if fsync is disabled from userspace.\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/9456a0ff5906cd2fcba41c731fb29dc99379df0c"},{"sha":"e8e787b4cfa5e4c1ad7d1aa3da39b51bfc0c9262","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"writeback: Fix occasional slow sync(1)\n\nIn case when system contains no dirty pages, wakeup_flusher_threads()\nwill submit WB_SYNC_NONE writeback for 0 pages so wb_writeback() exits\nimmediately without doing anything. Thus sync(1) will write all the\ndirty inodes from a WB_SYNC_ALL writeback pass which is slow.\n\nFix the problem by using get_nr_dirty_pages() in\nwakeup_flusher_threads() instead of calculating number of dirty pages\nmanually. That function also takes number of dirty inodes into account.\n\nCC: stable@vger.kernel.org\nReported-by: Paul Taysom <taysom@chromium.org>\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Cristoforo Cataldo <cristoforo.cataldo@gmail.com>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/e8e787b4cfa5e4c1ad7d1aa3da39b51bfc0c9262"},{"sha":"495e2c7e9684029dc015d8bd3943f3faea6509e6","author":{"email":"4d9e23a041ac966f5316a7481300d4ae12e806fe@redhat.com","name":"Dave Chinner"},"message":"sync: don't block the flusher thread waiting on IO\n\nWhen sync does it's WB_SYNC_ALL writeback, it issues data Io and\nthen immediately waits for IO completion. This is done in the\ncontext of the flusher thread, and hence completely ties up the\nflusher thread for the backing device until all the dirty inodes\nhave been synced. On filesystems that are dirtying inodes constantly\nand quickly, this means the flusher thread can be tied up for\nminutes per sync call and hence badly affect system level write IO\nperformance as the page cache cannot be cleaned quickly.\n\nWe already have a wait loop for IO completion for sync(2), so cut\nthis out of the flusher thread and delegate it to wait_sb_inodes().\nHence we can do rapid IO submission, and then wait for it all to\ncomplete.\n\nEffect of sync on fsmark before the patch:\n\nFSUse%        Count         Size    Files/sec     App Overhead\n.....\n     0       640000         4096      35154.6          1026984\n     0       720000         4096      36740.3          1023844\n     0       800000         4096      36184.6           916599\n     0       880000         4096       1282.7          1054367\n     0       960000         4096       3951.3           918773\n     0      1040000         4096      40646.2           996448\n     0      1120000         4096      43610.1           895647\n     0      1200000         4096      40333.1           921048\n\nAnd a single sync pass took:\n\n  real    0m52.407s\n  user    0m0.000s\n  sys     0m0.090s\n\nAfter the patch, there is no impact on fsmark results, and each\nindividual sync(2) operation run concurrently with the same fsmark\nworkload takes roughly 7s:\n\n  real    0m6.930s\n  user    0m0.000s\n  sys     0m0.039s\n\nIOWs, sync is 7-8x faster on a busy filesystem and does not have an\nadverse impact on ongoing async data write operations.\n\nSigned-off-by: Dave Chinner <dchinner@redhat.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/495e2c7e9684029dc015d8bd3943f3faea6509e6"},{"sha":"67e94d49d922779a267754a954b191bc2a40a0fc","author":{"email":"4b3f23b045e38e54cffd83d34440316666b35af9@codeaurora.org","name":"Stepan Moskovchenko"},"message":"ARM: Use -mcpu=cortex-a15 when targeting MSM Krait CPUs\n\nEnable compiler optimizations specific to the Cortex-A15\nprocessor when targeting MSM Krait CPUs. This is necessary\ntake advantage of the UDIV/SDIV instructions supported by\nthese processors. To accomplish this, we need to remove the\n-march=armv7-a ISA restriction from the compiler options\nbecause 'cortex-a15' is a superset of 'armv7-a'.\n\nChange-Id: I6215aecc11fb4f77c971de7b84f68649ef234357\nSigned-off-by: Stepan Moskovchenko <stepanm@codeaurora.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/67e94d49d922779a267754a954b191bc2a40a0fc"},{"sha":"4dfeb468415551e0b8f9fb0d14c20378530a765a","author":{"email":"adb0658383f88ec6beb1fb7689ba0dac7c1c4882@oracle.com","name":"Junxiao Bi"},"message":"writeback: fix race that cause writeback hung\n\nThere is a race between mark inode dirty and writeback thread, see the\nfollowing scenario.  In this case, writeback thread will not run though\nthere is dirty_io.\n\n__mark_inode_dirty()                                          bdi_writeback_workfn()\n\t...                                                       \t...\n\tspin_lock(&inode->i_lock);\n\t...\n\tif (bdi_cap_writeback_dirty(bdi)) {\n\t    <<< assume wb has dirty_io, so wakeup_bdi is false.\n\t    <<< the following inode_dirty also have wakeup_bdi false.\n\t    if (!wb_has_dirty_io(&bdi->wb))\n\t\t    wakeup_bdi = true;\n\t}\n\tspin_unlock(&inode->i_lock);\n\t                                                            <<< assume last dirty_io is removed here.\n\t                                                            pages_written = wb_do_writeback(wb);\n\t                                                            ...\n\t                                                            <<< work_list empty and wb has no dirty_io,\n\t                                                            <<< delayed_work will not be queued.\n\t                                                            if (!list_empty(&bdi->work_list) ||\n\t                                                                (wb_has_dirty_io(wb) && dirty_writeback_interval))\n\t                                                                queue_delayed_work(bdi_wq, &wb->dwork,\n\t                                                                    msecs_to_jiffies(dirty_writeback_interval * 10));\n\tspin_lock(&bdi->wb.list_lock);\n\tinode->dirtied_when = jiffies;\n\t<<< new dirty_io is added.\n\tlist_move(&inode->i_wb_list, &bdi->wb.b_dirty);\n\tspin_unlock(&bdi->wb.list_lock);\n\n\t<<< though there is dirty_io, but wakeup_bdi is false,\n\t<<< so writeback thread will not be waked up and\n\t<<< the new dirty_io will not be flushed.\n\tif (wakeup_bdi)\n\t    bdi_wakeup_thread_delayed(bdi);\n\nWriteback will run until there is a new flush work queued.  This may cause\na lot of dirty pages stay in memory for a long time.\n\nSigned-off-by: Junxiao Bi <junxiao.bi@oracle.com>\nReviewed-by: Jan Kara <jack@suse.cz>\nCc: Fengguang Wu <fengguang.wu@intel.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/4dfeb468415551e0b8f9fb0d14c20378530a765a"},{"sha":"39e595a9511c7927c5b43b2ebce7f918cd05b690","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\n\nSigned-off-by: Francisco Franco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/39e595a9511c7927c5b43b2ebce7f918cd05b690"},{"sha":"2e2316b2325016cff0665e530c62b19511d128c5","author":{"email":"d09719b174b1d7232763de9bbeaca66508591b55@codeaurora.org","name":"Sujit Reddy Thumma"},"message":"PM / QoS: Fix deadlock during PM QoS vote to default value\n\npm_qos_work_fn() calls pm_qos_update_request() which does\ncancel_delayed_work_sync() on the same pm_qos_work_fn()\ncausing deadlock. Fix this by updating the target with\ndefault timeout value directly instead of calling\npm_qos_update_request().\n\nCRs-Fixed: 526216\nChange-Id: I7de2fb1c89f87b0ebf7427116b8920aec50d5b2b\nSigned-off-by: Sujit Reddy Thumma <sthumma@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/2e2316b2325016cff0665e530c62b19511d128c5"},{"sha":"040df738c0b83a1bad3b9bc44d5b9cf2e0f57cc7","author":{"email":"24f7fe9d205c8a9f6ade0c2894e14303ca16087f@intel.com","name":"Fengguang Wu"},"message":"readahead: make context readahead more conservative\n\nThis helps performance on moderately dense random reads on SSD.\n\nTransaction-Per-Second numbers provided by Taobao:\n\n\t\tQPS\tcase\n\t\t-------------------------------------------------------\n\t\t7536\tdisable context readahead totally\nw/ patch:\t7129\tslower size rampup and start RA on the 3rd read\n\t\t6717\tslower size rampup\nw/o patch:\t5581\tunmodified context readahead\n\nBefore, readahead will be started whenever reading page N+1 when it happen\nto read N recently.  After patch, we'll only start readahead when *three*\nrandom reads happen to access pages N, N+1, N+2.  The probability of this\nhappening is extremely low for pure random reads, unless they are very\ndense, which actually deserves some readahead.\n\nAlso start with a smaller readahead window.  The impact to interleaved\nsequential reads should be small, because for a long run stream, the the\nsmall readahead window rampup phase is negletable.\n\nThe context readahead actually benefits clustered random reads on HDD\nwhose seek cost is pretty high.  However as SSD is increasingly used for\nrandom read workloads it's better for the context readahead to concentrate\non interleaved sequential reads.\n\nAnother SSD rand read test from Miao\n\n        # file size:        2GB\n        # read IO amount: 625MB\n        sysbench --test=fileio          \\\n                --max-requests=10000    \\\n                --num-threads=1         \\\n                --file-num=1            \\\n                --file-block-size=64K   \\\n                --file-test-mode=rndrd  \\\n                --file-fsync-freq=0     \\\n                --file-fsync-end=off    run\n\nshows the performance of btrfs grows up from 69MB/s to 121MB/s, ext4 from\n104MB/s to 121MB/s.\n\nSigned-off-by: Wu Fengguang <fengguang.wu@intel.com>\nTested-by: Tao Ma <tm@tao.ma>\nTested-by: Miao Xie <miaox@cn.fujitsu.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/040df738c0b83a1bad3b9bc44d5b9cf2e0f57cc7"},{"sha":"3a7b823006c7e16865bcc61dd0bac8c85f9ec59e","author":{"email":"596727c8a0ea4db3ba2ceceedccbacd3d7b371b8@suse.cz","name":"Jan Kara"},"message":"block: Reserve only one queue tag for sync IO if only 3 tags are available\n\nIn case a device has three tags available we still reserve two of them\nfor sync IO. That leaves only a single tag for async IO such as\nwriteback from flusher thread which results in poor performance.\n\nAllow async IO to consume two tags in case queue has three tag availabe\nto get a decent async write performance.\n\nThis patch improves streaming write performance on a machine with such disk\nfrom ~21 MB/s to ~52 MB/s. Also postmark throughput in presence of\nstreaming writer improves from 8 to 12 transactions per second so sync\nIO doesn't seem to be harmed in presence of heavy async writer.\n\nSigned-off-by: Jan Kara <jack@suse.cz>\nSigned-off-by: Jens Axboe <axboe@kernel.dk>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/3a7b823006c7e16865bcc61dd0bac8c85f9ec59e"},{"sha":"c5e89f5dab3940e1ab1fc087505b61b7d9430026","author":{"email":"3d00b54ad717112934d0b63b7ac2975b44022a61@I-love.SAKURA.ne.jp","name":"Tetsuo Handa"},"message":"SELinux: Fix memory leak upon loading policy\n\ncommit 8ed814602876bec9bad2649ca17f34b499357a1c upstream.\n\nHello.\n\nI got below leak with linux-3.10.0-54.0.1.el7.x86_64 .\n\n[  681.903890] kmemleak: 5538 new suspected memory leaks (see /sys/kernel/debug/kmemleak)\n\nBelow is a patch, but I don't know whether we need special handing for undoing\nebitmap_set_bit() call.\n----------\n>>From fe97527a90fe95e2239dfbaa7558f0ed559c0992 Mon Sep 17 00:00:00 2001\nFrom: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>\nDate: Mon, 6 Jan 2014 16:30:21 +0900\nSubject: SELinux: Fix memory leak upon loading policy\n\nCommit 2463c26d \"SELinux: put name based create rules in a hashtable\" did not\ncheck return value from hashtab_insert() in filename_trans_read(). It leaks\nmemory if hashtab_insert() returns error.\n\n  unreferenced object 0xffff88005c9160d0 (size 8):\n    comm \"systemd\", pid 1, jiffies 4294688674 (age 235.265s)\n    hex dump (first 8 bytes):\n      57 0b 00 00 6b 6b 6b a5                          W...kkk.\n    backtrace:\n      [<ffffffff816604ae>] kmemleak_alloc+0x4e/0xb0\n      [<ffffffff811cba5e>] kmem_cache_alloc_trace+0x12e/0x360\n      [<ffffffff812aec5d>] policydb_read+0xd1d/0xf70\n      [<ffffffff812b345c>] security_load_policy+0x6c/0x500\n      [<ffffffff812a623c>] sel_write_load+0xac/0x750\n      [<ffffffff811eb680>] vfs_write+0xc0/0x1f0\n      [<ffffffff811ec08c>] SyS_write+0x4c/0xa0\n      [<ffffffff81690419>] system_call_fastpath+0x16/0x1b\n      [<ffffffffffffffff>] 0xffffffffffffffff\n\nHowever, we should not return EEXIST error to the caller, or the systemd will\nshow below message and the boot sequence freezes.\n\n  systemd[1]: Failed to load SELinux policy. Freezing.\n\nSigned-off-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>\nAcked-by: Eric Paris <eparis@redhat.com>\nSigned-off-by: Paul Moore <pmoore@redhat.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/c5e89f5dab3940e1ab1fc087505b61b7d9430026"},{"sha":"f6b670e91577b0b88f9afef1babf59e96bceca30","author":{"email":"39ea6a09710987173e32e37c86918024a0f441c1@suse.de","name":"Mel Gorman"},"message":"mm: slub: Default slub_max_order to 0\n\nTo avoid locking and per-cpu overhead, SLUB optimisically uses\nhigh-order allocations up to order-3 by default and falls back to\nlower allocations if they fail. While care is taken that the caller\nand kswapd take no unusual steps in response to this, there are\nfurther consequences like shrinkers who have to free more objects to\nrelease any memory. There is anecdotal evidence that significant time\nis being spent looping in shrinkers with insufficient progress being\nmade (https://lkml.org/lkml/2011/4/28/361) and keeping kswapd awake.\n\nSLUB is now the default allocator and some bug reports have been\npinned down to SLUB using high orders during operations like\ncopying large amounts of data. SLUBs use of high-orders benefits\napplications that are sized to memory appropriately but this does not\nnecessarily apply to large file servers or desktops.  This patch\ncauses SLUB to use order-0 pages like SLAB does by default.\nThere is further evidence that this keeps kswapd's usage lower\n(https://lkml.org/lkml/2011/5/10/383).\n\nSigned-off-by: Mel Gorman <mgorman@suse.de>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/f6b670e91577b0b88f9afef1babf59e96bceca30"},{"sha":"09f7a54eedf5d887b04b471bb13632ddcbb845cb","author":{"email":"16a9a54ddf4259952e3c118c763138e83693d7fd@perches.com","name":"Joe Perches"},"message":"jiffies conversions: Use compile time constants when possible\n\nDo the multiplications and divisions at compile time\ninstead of runtime when the converted value is a constant.\n\nMake the calculation functions static __always_inline to jiffies.h.\n\nAdd #defines with __builtin_constant_p to test and use the\nstatic inline or the runtime functions as appropriate.\n\nPrefix the old exported symbols/functions with __\n\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/09f7a54eedf5d887b04b471bb13632ddcbb845cb"},{"sha":"3575bfc177680f0f9b86cf37fd8224e03d2ec9d4","author":{"email":"be5b96b982d71a0e8c9df1629ed76a94a416b6dd@codeaurora.org","name":"Hareesh Gundu"},"message":"msm: kgsl: Fix Z180 memory leak\n\nDecerement entry refcount, which incremented\nin kgsl_sharedmem_find_region.\n\nCRs-Fixed: 635747\nChange-Id: I621ba8f8e119a9ab8ba5455b28a565e3cae2f7cd\nSigned-off-by: Hareesh Gundu <hareeshg@codeaurora.org>\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/3575bfc177680f0f9b86cf37fd8224e03d2ec9d4"},{"sha":"8aac1d9fd86d3a5ff658851a43c834dda3a6523a","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"msm: cpu: add overclock up to 1728MHz\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/8aac1d9fd86d3a5ff658851a43c834dda3a6523a"},{"sha":"25d2d168a53fe1e39fda788281aee50ec558d0c6","author":{"email":"42480b5f4d505650064e5081b85d867a03559887@gmail.com","name":"franciscofranco"},"message":"power: why the useless log spam...\n\nSigned-off-by: franciscofranco <franciscofranco.1990@gmail.com>","distinct":true,"url":"https://api.github.com/repos/nasty007/kernel_msm/commits/25d2d168a53fe1e39fda788281aee50ec558d0c6"}]}