Enable ARCH_RANDOM
mm: Don't put CMA pages on per cpu lists

CMA allocations rely on being able to migrate pages out
quickly to fulfill the allocations. Most use cases for
movable allocations meet this requirement. File system
allocations may take an unaccpetably long time to
migrate, which creates delays from CMA. Prevent CMA
pages from ending up on the per-cpu lists to avoid
code paths grabbing CMA pages on the fast path. CMA
pages can still be allocated as a fallback under tight
memory pressure.
cma: Introduce and redirect page allocation to CMA
CMA pages are designed to be used as fallback for movable allocations
and cannot be used for non-movable allocations. If CMA pages are
utilized poorly, non-movable allocations may end up getting starved if
all regular movable pages are allocated and the only pages left are
CMA. Always using CMA pages first creates unacceptable performance
problems. As a midway alternative, use CMA pages for certain
userspace allocations. The userspace pages can be migrated or dropped
quickly which giving decent utilization.
Default Governor/Scheduler: Lulzactive (tweaked) / zen

According to my tests this combination with tweaked values provides the best performance and good battery life - for now
JBX-Kernel 3.4
headers: add missing CMA / defconfig: add new settings
reorganize config, cleanup doubled sync drivers, enable sync
default scheduler: VR

I figured that ZEN could cause freezes - not sure yet. Changew it to VR for now.
Revert "default scheduler: VR"

This reverts commit 208cb564a2eba4593dd6561637d3871b4ef458ba.
Revert "reorganize config, cleanup doubled sync drivers, enable sync"

This reverts commit 78b965bc5d0e50bd1296ef40a6892cc42c3ab517.
sync: remove doubled driver from staging section
defconfig: correct configuration now ..
Dyn Fsync: Enable by default - disables Async Fsync