GitHub PushEvent at 2014-09-07 18:07:48
Repository: NukedTrinity
Actor: pattyboi
Payload: {"shas":[["cbf0e956bfb485791b535207479322779b35e2ac","3e8c88a0c3c43122ff1294bc19840a139070b2cd@gmail.com","mm: implement memory compaction retries for high-order allocations\n\nTaken from Falcon (Motorola Moto G)\n\nConflicts:\n\tmm/page_alloc.c","sconosciuto",true],["bf08a1295ecb2e2fca82e610100db04b6274215f","f4f6ed1f4b62867ce26898e63a0cee63dab427c0@ti.com","mfd: Move omap-usb-host usbhs init before allocing child dev\n\nmfd: Move omap-usb-host usbhs init before allocing child dev\n\n[backported from p-android-omap-3.4]\n\nThere could be possible race condition where the host dev's\nare alloced and added to platform dev just before usbhs_init.\nJust move usbhs_init before adding child dev.\n\nChange-Id: I3c54db97f39c7714427e738560fba8076283e66d\nCC: Alan Stern <stern@rowland.harvard.edu>\nSigned-off-by: Govindraj.R <govindraj.raja@ti.com>\nAcked-by: Felipe Balbi <balbi@ti.com>\nSigned-off-by: Samuel Ortiz <sameo@linux.intel.com>","Govindraj.R",true],["d23073bfd4128c3cb3cef7e6f61841cb3da5f337","cb3904095a5bc20edc93ba3dfa3e7d27d981b654@intel.com","vmscan: add block plug for page reclaim\n\nper-task block plug can reduce block queue lock contention and increase\nrequest merge.  Currently page reclaim doesn't support it.  I originally\nthought page reclaim doesn't need it, because kswapd thread count is\nlimited and file cache write is done at flusher mostly.\n\nWhen I test a workload with heavy swap in a 4-node machine, each CPU is\ndoing direct page reclaim and swap.  This causes block queue lock\ncontention.  In my test, without below patch, the CPU utilization is about\n2% ~ 7%.  With the patch, the CPU utilization is about 1% ~ 3%.  Disk\nthroughput isn't changed.  This should improve normal kswapd write and\nfile cache write too (increase request merge for example), but might not\nbe so obvious as I explain above.\n\nChange-Id: Ic02b467c30a1e924026e05dd488f631ba70702e0\nSigned-off-by: Shaohua Li <shaohua.li@intel.com>\nCc: Jens Axboe <axboe@kernel.dk>\nCc: Minchan Kim <minchan.kim@gmail.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>","Shaohua Li",true],["661d2583465b5925aa59fa411a7e0356a733a3c1","3e8c88a0c3c43122ff1294bc19840a139070b2cd@gmail.com","mm: compact memory on early suspend\n\nTaken from Falcon (Motorola Moto G)","sconosciuto",true],["7c0c41374c1a102c7223b6112d0bb835f184848b","7eae7c015abe6cfbcb55fd218cc6b352105b3f52@gmail.com","sched/rt: Avoid updating RT entry timeout twice within one tick period\n\nThe issue below was found in 2.6.34-rt rather than mainline rt\nkernel, but the issue still exists upstream as well.\n\nSo please let me describe how it was noticed on 2.6.34-rt:\n\nOn this version, each softirq has its own thread, it means there\nis at least one RT FIFO task per cpu. The priority of these\ntasks is set to 49 by default. If user launches an RT FIFO task\nwith priority lower than 49 of softirq RT tasks, it's possible\nthere are two RT FIFO tasks enqueued one cpu runqueue at one\nmoment. By current strategy of balancing RT tasks, when it comes\nto RT tasks, we really need to put them off to a CPU that they\ncan run on as soon as possible. Even if it means a bit of cache\nline flushing, we want RT tasks to be run with the least latency.\n\nWhen the user RT FIFO task which just launched before is\nrunning, the sched timer tick of the current cpu happens. In this\ntick period, the timeout value of the user RT task will be\nupdated once. Subsequently, we try to wake up one softirq RT\ntask on its local cpu. As the priority of current user RT task\nis lower than the softirq RT task, the current task will be\npreempted by the higher priority softirq RT task. Before\npreemption, we check to see if current can readily move to a\ndifferent cpu. If so, we will reschedule to allow the RT push logic\nto try to move current somewhere else. Whenever the woken\nsoftirq RT task runs, it first tries to migrate the user FIFO RT\ntask over to a cpu that is running a task of lesser priority. If\nmigration is done, it will send a reschedule request to the found\ncpu by IPI interrupt. Once the target cpu responds the IPI\ninterrupt, it will pick the migrated user RT task to preempt its\ncurrent task. When the user RT task is running on the new cpu,\nthe sched timer tick of the cpu fires. So it will tick the user\nRT task again. This also means the RT task timeout value will be\nupdated again. As the migration may be done in one tick period,\nit means the user RT task timeout value will be updated twice\nwithin one tick.\n\nIf we set a limit on the amount of cpu time for the user RT task\nby setrlimit(RLIMIT_RTTIME), the SIGXCPU signal should be posted\nupon reaching the soft limit.\n\nBut exactly when the SIGXCPU signal should be sent depends on the\nRT task timeout value. In fact the timeout mechanism of sending\nthe SIGXCPU signal assumes the RT task timeout is increased once\nevery tick.\n\nHowever, currently the timeout value may be added twice per\ntick. So it results in the SIGXCPU signal being sent earlier\nthan expected.\n\nTo solve this issue, we prevent the timeout value from increasing\ntwice within one tick time by remembering the jiffies value of\nlast updating the timeout. As long as the RT task's jiffies is\ndifferent with the global jiffies value, we allow its timeout to\nbe updated.\n\nSigned-off-by: Ying Xue <ying.xue@windriver.com>\nSigned-off-by: Fan Du <fan.du@windriver.com>\nReviewed-by: Yong Zhang <yong.zhang0@gmail.com>\nAcked-by: Steven Rostedt <rostedt@goodmis.org>\nCc: <peterz@infradead.org>\nLink: http://lkml.kernel.org/r/1342508623-2887-1-git-send-email-ying.xue@windriver.com\nSigned-off-by: Ingo Molnar <mingo@kernel.org>\n[ lizf: backported to 3.4: adjust context ]\nSigned-off-by: Li Zefan <lizefan@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nbackport to 3.0: Boy Petersen <boypetersen@gmail.com>","Boy Petersen",true],["db8c0b9a92c76d357c81f780418616773500a0fe","7eae7c015abe6cfbcb55fd218cc6b352105b3f52@gmail.com","cgroup: fix RCU accesses to task->cgroups\n\ntask->cgroups is a RCU pointer pointing to struct css_set.  A task\nswitches to a different css_set on cgroup migration but a css_set\ndoesn't change once created and its pointers to cgroup_subsys_states\naren't RCU protected.\n\ntask_subsys_state[_check]() is the macro to acquire css given a task\nand subsys_id pair.  It RCU-dereferences task->cgroups->subsys[] not\ntask->cgroups, so the RCU pointer task->cgroups ends up being\ndereferenced without read_barrier_depends() after it.  It's broken.\n\nFix it by introducing task_css_set[_check]() which does\nRCU-dereference on task->cgroups.  task_subsys_state[_check]() is\nreimplemented to directly dereference ->subsys[] of the css_set\nreturned from task_css_set[_check]().\n\nThis removes some of sparse RCU warnings in cgroup.\n\nv2: Fixed unbalanced parenthsis and there's no need to use\n    rcu_dereference_raw() when !CONFIG_PROVE_RCU.  Both spotted by Li.\n\nSigned-off-by: Tejun Heo <tj@kernel.org>\nReported-by: Fengguang Wu <fengguang.wu@intel.com>\nAcked-by: Li Zefan <lizefan@huawei.com>\n[bwh: Backported to 3.2:\n - Adjust context\n - Remove CONFIG_PROVE_RCU condition\n - s/lockdep_is_held(&cgroup_mutex)/cgroup_lock_is_held()/]\nSigned-off-by: Ben Hutchings <ben@decadent.org.uk>\nCc: Qiang Huang <h.huangqiang@huawei.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nbackport to 3.0: Boy Petersen <boypetersen@gmail.com>","Boy Petersen",true],["6a52d5ce2293b97dd872a099374cf481dd987d18","10ad854332e763177fdf56644e47c43fe37a6f74@gmail.com","mmc core : increase limit_us","googyanas",true],["e2a579d4ebabf4370e98c73d57115a5a495c1ea0","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","squash some memory/writeback stuff","pattyboi",true],["a6be684a51240b1df360b16bbd0c3ac9412dbd07","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","defconfig","pattyboi",true],["599efed867266f3fef6a1bd574f86b48d6b1c169","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","force block to be non-rotational for better performance","pattyboi",true],["44655a073baa2d1c4425745a3c1916fb03445b44","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","disable hotplug build","pattyboi",true],["8cbbd9d6a9883acff82fd4053c56febd95061fd1","114d53767672d1f542671c183e5305b5310ca7af@ti.com","SGX-KM (hack): Workaround for kernel panic due to invalid sync objects\n\nThis fixes a problem when invalid syncobjects are accessed after the\nswap chain has been destroyed. Should be reverted when final fix\nis in place.\n\nChange-Id: Iff4c23534e16f6a2ff86bfdf3a9c5dd33320e5cb\nAuthor:    Kostiantyn Luzan <kostiantyn.luzan@ti.com>\nSigned-off-by: Hemant Hariyani <hemanthariyani@ti.com>\nSigned-off-by: Tate Hornbeck <tate.hornbeck@ti.com>","Kostiantyn Luzan",true],["b4150b073635b321fc3c3ab77b8f34d98f82825a","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","misc wifi updates from the 3.10 repo (very little things)","pattyboi",true],["6ef391e7450b05db339a5a8326969a7cf03f9c30","9ae03fa0527c30dd0044e74ed4dc0d3552c8ce20@gmail.com","bmp180: Report ambient temperature through ABS_MISC.\n\nChange-Id: I2439ca6f40b4f16128941cc5bc5f41f95805e32f\nSigned-off-by: Kyle Repinski <repinski23@gmail.com>","Kyle Repinski",true],["96e5077f74241ba2f699adeccbb5bf6178c3f542","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","squash omap4:pm:pwrst updates from oz kernel","pattyboi",true],["dc72fa5de65f3dee44191add647d7a711df29a44","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","force enable frandom","pattyboi",true],["a82858bc22b555b5a6e35174f9d6d00fe96e6c7c","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","since we hotplug,this is printed everytime a cpu is brought up because its a smp function,comment it out so we dont get log spamming","pattyboi",true],["ca94955bb971ed57946013db07b61d4d0a9a5fce","5df8b7afbc8bc60e3df630fdc676a579bee7328f@gmail.com","mm: Dynamic management of dirty page writebacks\n\nThis feature allows to have two different intervals for dirty page\nwritebacks and to dynamically manage them when the system has been\nresumed (it's active) or when has been suspended.\n\nThree new procfs parameters are exposed inside /proc/sys/vm path:\n- \"dynamic_dirty_writeback\" is the activation status of this feature,\n  set 1 to enable it, set 0 to disable it and use the standard behaviour\n- \"dirty_writeback_active_centisecs\" is the interval for the dirty page\n  writebacks when the system is active (screen on)\n- \"dirty_writeback_suspend_centisecs\" is the interval for the dirty page\n  writebacks when the system is suspended (screen off)\n\nThis feature is in part inspired on Francisco Franco's patch:\nhttps://github.com/franciscofranco/mako/commit/34d79548cf16b69c7d0154836018e7f258a22947\n\nSigned-off-by: Cristoforo Cataldo <cristoforo.cataldo@gmail.com>\nSigned-off-by: Dan Trifan <jimsth@gmail.com>\n\nConflicts:\n\tmm/Kconfig\n\tmm/page-writeback.c","Cristoforo Cataldo",true],["9517aa8e7c4d485d4eb578b3cc78b0e37a326a01","925aa76529e740fe0d5152049d90ba90ccc9d68b@gmail.com","defconfig","pattyboi",true]],"size":19,"ref":"refs/heads/new","head":"9517aa8e7c4d485d4eb578b3cc78b0e37a326a01"}