Tune Interactive CPU GOV.
crypto: lzo - try kmalloc() before vmalloc()

zswap allocates one LZO context per online cpu.

Using vmalloc() for small (16KB) memory areas has drawback of slowing
down /proc/vmallocinfo and /proc/meminfo reads, TLB pressure and poor
NUMA locality, as default NUMA policy at boot time is to interleave
pages :

edumazet:~# grep lzo /proc/vmallocinfo | head -4
0xffffc90006062000-0xffffc90006067000   20480 lzo_init+0x1b/0x30 pages=4 vmalloc N0=2 N1=2
0xffffc90006067000-0xffffc9000606c000   20480 lzo_init+0x1b/0x30 pages=4 vmalloc N0=2 N1=2
0xffffc9000606c000-0xffffc90006071000   20480 lzo_init+0x1b/0x30 pages=4 vmalloc N0=2 N1=2
0xffffc90006071000-0xffffc90006076000   20480 lzo_init+0x1b/0x30 pages=4 vmalloc N0=2 N1=2

This patch tries a regular kmalloc() and fallback to vmalloc in case
memory is too fragmented.

Signed-off-by: Eric Dumazet <edumazet@google.com>
Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au>
Signed-off-by: Pranav Vashi <neobuddy89@gmail.com>
cfg80211: mlme: Silently ignore duplicate management registrations

Instead of erroring out, just ignore the call

Change-Id: I5ff67100ea2d7f53bd30b6844c462bca71c24d15
Config cleanups. removed unused DECOMPRESS and enabled LGE_HANDLE_PANIC

LGE_HANDLE_PANIC will help to understand logs some more.
KERNEL HOTPLUGS: added control for Suspend or Always active! read more.

Some of my users report that they cant wake the device in random cases.
All started when i have fixed the suspend mode as it's was not working
for long time.
But in the same time a lot of people reported all good and stable!
including me when using the hotplugs in suspend mode. no SODS!

So by default it's should be active, OK! let it be active.
I have added STweaks control for it. with info and warnings.
Also using hotplug in active mode,
will allow faster screen wake when call is coming in.
Need to check battery but i dont think it's really major saver...

* Additionally i have remove the cpu boost when suspend is canceled
it's seems that in some condition we get NULL error on _cpu_up
so use the boost only after real suspend time...