Merge branches 'fix/arizona', 'fix/cs4271', 'fix/kirkwood' and 'fix/samsung'...

-----------------------------------------------------------------------

0000000000000000	0000007fffffffff	 512GB		user

ffffff8000000000	ffffffbbfffcffff	~240GB		vmalloc

ffffff8000000000	ffffffbbfffeffff	~240GB		vmalloc

ffffffbbfffd0000	ffffffbcfffdffff	  64KB		[guard page]

ffffffbbffff0000	ffffffbbffffffff	  64KB		[guard page]

ffffffbbfffe0000	ffffffbcfffeffff	  64KB		PCI I/O space

ffffffbc00000000	ffffffbdffffffff	   8GB		vmemmap

ffffffbbffff0000	ffffffbcffffffff	  64KB		[guard page]

ffffffbe00000000	ffffffbffbbfffff	  ~8GB		[guard, future vmmemap]

ffffffbc00000000	ffffffbdffffffff	   8GB		vmemmap

ffffffbffbe00000	ffffffbffbe0ffff	  64KB		PCI I/O space

ffffffbe00000000	ffffffbffbffffff	  ~8GB		[guard, future vmmemap]

ffffffbbffff0000	ffffffbcffffffff	  ~2MB		[guard]

ffffffbffc000000	ffffffbfffffffff	  64MB		modules

5.3 swappiness

Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.

Please note that unlike the global swappiness, memcg knob set to 0

really prevents from any swapping even if there is a swap storage

available. This might lead to memcg OOM killer if there are no file

pages to reclaim.

Following cgroups' swappiness can't be changed.

- root cgroup (uses /proc/sys/vm/swappiness).

* EETI eGalax Multiple Touch Controller

Required properties:

- compatible: must be "eeti,egalax_ts"

- reg: i2c slave address

- interrupt-parent: the phandle for the interrupt controller

- interrupts: touch controller interrupt

- wakeup-gpios: the gpio pin to be used for waking up the controller

  as well as uased as irq pin

Example:

	egalax_ts@04 {

		compatible = "eeti,egalax_ts";

		reg = <0x04>;

		interrupt-parent = <&gpio1>;

		interrupts = <9 2>;

		wakeup-gpios = <&gpio1 9 0>;

	};

  2	Modifying System Parameters

  3	Per-Process Parameters

  3.1	/proc/<pid>/oom_score_adj - Adjust the oom-killer

  3.1	/proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer

								score

  3.2	/proc/<pid>/oom_score - Display current oom-killer score

  3.3	/proc/<pid>/io - Display the IO accounting fields

CHAPTER 3: PER-PROCESS PARAMETERS

------------------------------------------------------------------------------

3.1 /proc/<pid>/oom_score_adj- Adjust the oom-killer score

3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj- Adjust the oom-killer score

--------------------------------------------------------------------------------

This file can be used to adjust the badness heuristic used to select which

These file can be used to adjust the badness heuristic used to select which

process gets killed in out of memory conditions.

The badness heuristic assigns a value to each candidate task ranging from 0

equivalent to discounting 50% of the task's allowed memory from being considered

as scoring against the task.

For backwards compatibility with previous kernels, /proc/<pid>/oom_adj may also

be used to tune the badness score.  Its acceptable values range from -16

(OOM_ADJUST_MIN) to +15 (OOM_ADJUST_MAX) and a special value of -17

(OOM_DISABLE) to disable oom killing entirely for that task.  Its value is

scaled linearly with /proc/<pid>/oom_score_adj.

The value of /proc/<pid>/oom_score_adj may be reduced no lower than the last

value set by a CAP_SYS_RESOURCE process. To reduce the value any lower

requires CAP_SYS_RESOURCE.

-------------------------------------------------------------

This file can be used to check the current score used by the oom-killer is for

any given <pid>.

any given <pid>. Use it together with /proc/<pid>/oom_score_adj to tune which

process should be killed in an out-of-memory situation.

3.3  /proc/<pid>/io - Display the IO accounting fields

-------------------------------------------------------

  BIOS and Kernel Developer's Guide (BKDG) For AMD Family 15h Processors

    (not yet published)

Author: Andreas Herrmann <andreas.herrmann3@amd.com>

Author: Andreas Herrmann <herrmann.der.user@googlemail.com>

Description

-----------