Lost in merge
Added improved glibc memcpy and memmove functions.

Signed-off-by: Dan Trifan <jimsth@gmail.com>
ARM: cpu topology: Enable ARCH_POWER
memcopy optimize
ARM-accelerated versions of selected functions from <string.h>
--bavison

Conflicts:
	mm/Makefile
 ARM: 7592/1: nommu: prevent generation of kernel unaligned memory acc… …

…esses

Recent ARMv7 toolchains assume that unaligned memory accesses will not
fault and will instead be handled by the processor.

For the nommu case (without an MPU), memory will be treated as
strongly-ordered and therefore unaligned accesses may fault regardless
of the SCTLR.A setting.

This patch passes -mno-unaligned-access to GCC when compiling for nommu
targets, preventing the generation of unaligned memory access in the
kernel.

Acked-by: Nicolas Pitre <nico@linaro.org>
Tested-by: Jonathan Austin <jonathan.austin@arm.com>
Signed-off-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>

b7cf3bce53 Browse code
Will Deacon authored a year ago

====================================

 BUILDFLAGS: optimize for armv7-a, cortex-a8
c8034bb3da Browse code
Talustus authored 10 months ago
add ondemandplus governor

Signed-off-by: Dan Trifan <jimsth@gmail.com>

Conflicts:
	drivers/cpufreq/Kconfig
	include/linux/cpufreq.h
ondemandplus: add and enable io_is_busy=2 option, adjust up_threshold and down_differential

Signed-off-by: Dan Trifan <jimsth@gmail.com>
ondemandplus governor: remove adaptive timer_rate logic

It is unlikely this gives any power savings and only
add some ugly code :)

Signed-off-by: Dan Trifan <jimsth@gmail.com>
cpufreq: added HYPER governor

Conflicts:
	drivers/cpufreq/Kconfig
	drivers/cpufreq/Makefile
Added Dynamic Interactive Governor
cpufreq: Add Sakuractive governor
cpufreq: hotplug: don't synch threads on jiffies

cpufreq-hotplug was always designed to run as a single thread that takes
aggregate load of all CPUs into account.  As such there is no need to
synchronize multiple threads to execute at the same time.  This
sychronization mechanism also causes execution of the do_dbs_check function
to be somewhat erratically scheduled.  Removing it causes scheduling of this
function to reliably happen based soley on the supplied sampling_rate
parameter.

Change-Id: If0edc89996f0d5763502236b225835dd9f4ab3c9
Signed-off-by: Mike Turquette <mturquette@ti.com>
cpufreq_hotplug.c: Update to last Cylon Kernel
added adaptive governor

Conflicts:
	drivers/cpufreq/Kconfig
	drivers/cpufreq/Makefile

Conflicts:
	drivers/cpufreq/Kconfig
	drivers/cpufreq/Makefile
	include/linux/cpufreq.h
Added ondemandX Governor

Conflicts:
	drivers/cpufreq/Kconfig
	drivers/cpufreq/Makefile
	include/linux/cpufreq.h
nohz: Remove nohz_cpu_mask

RCU no longer uses this global variable, nor does anyone else.  This
commit therefore removes this variable.  This reduces memory footprint
and also removes some atomic instructions and memory barriers from
the dyntick-idle path.

Signed-off-by: Alex Shi <alex.shi@intel.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
lowmemorykiller: updates from 3.4 kernel

Signed-off-by: Dan Trifan <jimsth@gmail.com>
logger: Add an enable toggle for entry storage; TNX AndreiLux and Dorimanx

You can disable logging by echo-ing 0 in /sys/module/logger/parameters/log_enabled
By default the logging is enabled.

Signed-off-by: Dan Trifan <jimsth@gmail.com>
staging: android: lowmemorykiller: Management of not killable processes

This feature allows the user to define processes and system processes
white-lists filled with the preferred process names and to not be killed
by lowmemorykiller, unless it is absolutely necessary.

This feature exposes four new lowmemorykiller parameters:
- donotkill_proc, is the flag to enable / disable this feature for the
  processes chosen by the user
- donotkill_sysproc, is the flag to enable / disable this feature for the
  system processes chosen by the user
- donotkill_proc_names, is the list of process names (comma separated)
  chosen by the user to be preserved from killing
- donotkill_sysproc_names, is the list of user system process names (comma separated)
  chosen by the user to be preserved from killing

When a the lowmemorykiller needs to free ram, it will first kill the processes
not included inside the two process name lists chosen by the user.
If there are no more standard killable processes, then it will be necessary to
kill one of the processes included inside one of the two white-lists, to
prevent system hangs, slowdowns, etc.

Signed-off-by: Dan Trifan <jimsth@gmail.com>