defconfig: add empty CROSS_COMPILE flag

Change-Id: Ibc83ded8711418a17ee32dedac72261e23b5dedd
Makefile: add optimization flags

Conflicts:
	Makefile

Change-Id: I2d630fb35a1c2f72b9ad9244ee8674facd8b0fa2
I/O Schedulers: add BFQ & VR
Governors: add SmartassV2, Badass, Lionheart, InteractiveX2 & Lagfree
added CPU freq governor wheatley (thanks to @Ezekeel)
block: add simple io scheduler

Conflicts:
	block/Makefile
block: fiops ioscheduler core FIOPS (Fair IOPS) ioscheduler is IOPS based ioscheduler, so only targets for drive without I/O seek. It's quite similar like CFQ, but the dispatch decision is made according to IOPS instead of slice.

The algorithm is simple. Drive has a service tree, and each task lives in
the tree. The key into the tree is called vios (virtual I/O). Every request
has vios, which is calculated according to its ioprio, request size and so
on. Task's vios is the sum of vios of all requests it dispatches. FIOPS
always selects task with minimum vios in the service tree and let the task
dispatch request. The dispatched request's vios is then added to the task's
vios and the task is repositioned in the sevice tree.

Unlike CFQ, FIOPS doesn't have separate sync/async queues, because with I/O
less writeback, usually a task can only dispatch either sync or async requests.
Bias read or write request can still be done with read/write scale.

One issue is if workload iodepth is lower than drive queue_depth, IOPS
share of a task might not be strictly according to its priority, request
size and so on. In this case, the drive is in idle actually. Solving the
problem need make drive idle, so impact performance. I believe CFQ isn't
completely fair between tasks in such case too.

Signed-off-by: Shaohua Li <shaohua.li@intel.com>

Conflicts:
	block/Makefile
defconfig: enable new CPU Governors & I/O Schedulers

Change-Id: I0e0197ddd42047112daa6fb6a0ebdf8b8b025c3e