Initramfs naming STE --> u8500
Update defconfigs
cpufreq: interactive: fix wrong tunables

since we aren't using extended cpufreqs, switch this up a bit.

Change-Id: Iafa0fceafd8985635928b9ef3be176ae038a5b45
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
fix initramfs reference

Change-Id: I30b5e9aea4e9c5fbaf755f4fea5b78310ed4c91c
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
fs: add universal exfat driver

this is much more updated and universal than the current exfat driver. furthermore, it should be in fs.

Change-Id: Iee912807399d5aae5ff43d252810c97782251241
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
drivers: remove old exfat driver

Change-Id: I94eef7ac6ae9dd3b7e84a31450d1c0a17db085e8
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
ARM: mach-ux500: Kconfig: fix incorrect u8500_hotplug option

Change-Id: Id6abc0d1317247d7febf53fa98837d661c4230b2
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
defconfigs: enable new exfat driver

Change-Id: I40cbdef9c6ccce6e324742b34440b400aa3f83bf
Reserve one more step for 1250 MHz

We enabled 100 MHz by default and we need one more step reserved to fit every freq step
defconfigs: enable lz4 compression support

Change-Id: I79f04f3f0870d9528c5b10deb795081d92286cbb
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
mm: vmscan: If kswapd has been running too long, allow it to sleep

Under constant allocation pressure, kswapd can be in the situation where
sleeping_prematurely() will always return true even if kswapd has been
running a long time. Check if kswapd needs to be scheduled.

Signed-off-by: Mel Gorman <mgorman@suse.de>
HACK: selinux: Make sure valid sk->sk_security

 - check valid sk->sk_security pointer in sock_has_perm to avoid NULL
   pointer dereference.

Inspired by conversation on Security Enhanced Android developers'
mailing list:

http://comments.gmane.org/gmane.comp.security.seandroid/1110

Change-Id: I548a0a7f30b48d5bab7460ee4a9a69aa45600f0a
Signed-off-by: Hong-Mei Li <a21834@motorola.com>
Reviewed-on: http://gerrit.pcs.mot.com/574782
SLTApproved: Slta Waiver <sltawvr@motorola.com>
Tested-by: Jira Key <jirakey@motorola.com>
Reviewed-by: Check Patch <CHEKPACH@motorola.com>
Reviewed-by: Jeffrey Carlyle <jeff.carlyle@motorola.com>
Submit-Approved: Jira Key <jirakey@motorola.com>
Reviewed-on: http://gerrit.pcs.mot.com/576126
Revert "block: Tweak deadline and cfq tunables"

This reverts commit 0ed66cfbbb01b7033012af0699125142235f0ef4.
block: tweak deadline scheduler again

Change-Id: I521e5900882475cad63c7b01e74b6036781950d1
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
sioplus: relax sync_read_expire, tighten sync_write_expire
Revert "sioplus: tweak writes_tarved for new memory updates"

This reverts commit 6900fb4f27a68c5da223c744cbb30bc304c2f387.
block: recursive merge requests

In a workload, thread 1 accesses a, a+2, ..., thread 2 accesses a+1, a+3,....
When the requests are flushed to queue, a and a+1 are merged to (a, a+1), a+2
and a+3 too to (a+2, a+3), but (a, a+1) and (a+2, a+3) aren't merged.

If we do recursive merge for such interleave access, some workloads throughput
get improvement. A recent worload I'm checking on is swap, below change
boostes the throughput around 5% ~ 10%.

Signed-off-by: Shaohua Li <shli@fusionio.com>
Signed-off-by: Jens Axboe <axboe@kernel.dk>
iosched: prevent aliased requests from starving other I/O

Hi, Jens,

If you recall, I posted an RFC patch for this back in July of last year:
http://lkml.org/lkml/2010/7/13/279

The basic problem is that a process can issue a never-ending stream of
async direct I/Os to the same sector on a device, thus starving out
other I/O in the system (due to the way the alias handling works in both
cfq and deadline).  The solution I proposed back then was to start
dispatching from the fifo after a certain number of aliases had been
dispatched.  Vivek asked why we had to treat aliases differently at all,
and I never had a good answer.  So, I put together a simple patch which
allows aliases to be added to the rb tree (it adds them to the right,
though that doesn't matter as the order isn't guaranteed anyway).  I
think this is the preferred solution, as it doesn't break up time slices
in CFQ or batches in deadline.  I've tested it, and it does solve the
starvation issue.  Let me know what you think.

Cheers,
Jeff

Signed-off-by: Jeff Moyer <jmoyer@redhat.com>
Signed-off-by: Jens Axboe <jaxboe@fusionio.com>
cpufreq: interactive: reduce micro stuttering

Change-Id: I77b330009984ebb7a540e1e84e5f8dbe772f59d2
Signed-off-by: Zhao Wei Liew <zhaoweiliew@gmail.com>
Revert "mm: Dynamic management of dirty page writebacks"

having a longer interval between writebacks can cause dirty pages to be swapped before being synchronised between cache and disk, thus causing data loss.
This reverts commit ea290e32d1d3735926747a5c464ccfe3ca927233.