{"push_id":659182500,"size":3,"distinct_size":3,"ref":"refs/heads/lollipop-caf","head":"26f058e2b4b2f5959897303d4391af149c09bc78","before":"607f779f7523e375c3818941fcb743eff95b81c3","commits":[{"sha":"b2af91bffb6d4631c72743fb5b8e72bdeffa02d1","author":{"email":"e296756d5edaffcdbc7b9904859492ff25d3fce5@linux.vnet.ibm.com","name":"Peter Oberparleiter"},"message":"x86, hweight: Fix BUG when booting with CONFIG_GCOV_PROFILE_ALL=y\n\ncommit 6583327c4dd55acbbf2a6f25e775b28b3abf9a42 upstream.\n\nCommit d61931d89b, \"x86: Add optimized popcnt variants\" introduced\ncompile flag -fcall-saved-rdi for lib/hweight.c. When combined with\noptions -fprofile-arcs and -O2, this flag causes gcc to generate\nbroken constructor code. As a result, a 64 bit x86 kernel compiled\nwith CONFIG_GCOV_PROFILE_ALL=y prints message \"gcov: could not create\nfile\" and runs into sproadic BUGs during boot.\n\nThe gcc people indicate that these kinds of problems are endemic when\nusing ad hoc calling conventions.  It is therefore best to treat any\nfile compiled with ad hoc calling conventions as an isolated\nenvironment and avoid things like profiling or coverage analysis,\nsince those subsystems assume a \"normal\" calling conventions.\n\nThis patch avoids the bug by excluding lib/hweight.o from coverage\nprofiling.\n\nReported-by: Meelis Roos <mroos@linux.ee>\nCc: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Peter Oberparleiter <oberpar@linux.vnet.ibm.com>\nLink: http://lkml.kernel.org/r/52F3A30C.7050205@linux.vnet.ibm.com\nSigned-off-by: H. Peter Anvin <hpa@zytor.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/b2af91bffb6d4631c72743fb5b8e72bdeffa02d1"},{"sha":"56ecaec7f2312ee0e4bbab2795b9a199396440b7","author":{"email":"c1b6782c4af8f0673da8923a0702a1832e5940f4@ffwll.ch","name":"Daniel Vetter"},"message":"drm/i915: kick any firmware framebuffers before claiming the gtt\n\ncommit 9f846a16d213523fbe6daea17e20df6b8ac5a1e5 upstream.\n\nEspecially vesafb likes to map everything as uc- (yikes), and if that\nmapping hangs around still while we try to map the gtt as wc the\nkernel will downgrade our request to uc-, resulting in abyssal\nperformance.\n\nUnfortunately we can't do this as early as readon does (i.e. as the\nfirst thing we do when initializing the hw) because our fb/mmio space\nregion moves around on a per-gen basis. So I've had to move it below\nthe gtt initialization, but that seems to work, too. The important\nthing is that we do this before we set up the gtt wc mapping.\n\nNow an altogether different question is why people compile their\nkernels with vesafb enabled, but I guess making things just work isn't\nbad per se ...\n\nv2:\n- s/radeondrmfb/inteldrmfb/\n- fix up error handling\n\nv3: Kill #ifdef X86, this is Intel after all. Noticed by Ben Widawsky.\n\nv4: Jani Nikula complained about the pointless bool primary\ninitialization.\n\nv5: Don't oops if we can't allocate, noticed by Chris Wilson.\n\nv6: Resolve conflicts with agp rework and fixup whitespace.\n\nThis is commit e188719a2891f01b3100d in drm-next.\n\nBackport to 3.5 -fixes queue requested by Dave Airlie - due to grub\nusing vesa on fedora their initrd seems to load vesafb before loading\nthe real kms driver. So tons more people actually experience a\ndead-slow gpu. Hence also the Cc: stable.\n\nReported-and-tested-by: \"Kilarski, Bernard R\" <bernard.r.kilarski@intel.com>\nReviewed-by: Chris Wilson <chris@chris-wilson.co.uk>\nSigned-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>\nSigned-off-by: Dave Airlie <airlied@redhat.com>\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>","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/56ecaec7f2312ee0e4bbab2795b9a199396440b7"},{"sha":"26f058e2b4b2f5959897303d4391af149c09bc78","author":{"email":"5c1e68b099950c134891f0b6e179498a8ebe9cf9@linux-foundation.org","name":"Andrew Morton"},"message":"mm/page_alloc.c: remove pageblock_default_order()\n\ncommit 955c1cd7401565671b064e499115344ec8067dfd upstream.\n\nThis has always been broken: one version takes an unsigned int and the\nother version takes no arguments.  This bug was hidden because one\nversion of set_pageblock_order() was a macro which doesn't evaluate its\nargument.\n\nSimplify it all and remove pageblock_default_order() altogether.\n\nReported-by: rajman mekaco <rajman.mekaco@gmail.com>\nCc: Mel Gorman <mel@csn.ul.ie>\nCc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>\nCc: Tejun Heo <tj@kernel.org>\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>\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>\n\nConflicts:\n\tmm/page_alloc.c","distinct":true,"url":"https://api.github.com/repos/smac0628/android_kernel_htc_msm8974/commits/26f058e2b4b2f5959897303d4391af149c09bc78"}]}