Merge "DOWNSTREAM: Merge AU239 commit...

		/sys/devices/system/cpu/vulnerabilities/meltdown

		/sys/devices/system/cpu/vulnerabilities/spectre_v1

		/sys/devices/system/cpu/vulnerabilities/spectre_v2

		/sys/devices/system/cpu/vulnerabilities/spec_store_bypass

Date:		January 2018

Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>

Description:	Information about CPU vulnerabilities

Contact:	"Jaegeuk Kim" <jaegeuk@kernel.org>

Description:

		 Controls the trimming rate in batch mode.

		 <deprecated>

What:		/sys/fs/f2fs/<disk>/cp_interval

Date:		October 2015

			allow data leaks with this option, which is equivalent

			to spectre_v2=off.

	nospec_store_bypass_disable

			[HW] Disable all mitigations for the Speculative Store Bypass vulnerability

	noxsave		[BUGS=X86] Disables x86 extended register state save

			and restore using xsave. The kernel will fallback to

			enabling legacy floating-point and sse state.

			Not specifying this option is equivalent to

			spectre_v2=auto.

	spec_store_bypass_disable=

			[HW] Control Speculative Store Bypass (SSB) Disable mitigation

			(Speculative Store Bypass vulnerability)

			Certain CPUs are vulnerable to an exploit against a

			a common industry wide performance optimization known

			as "Speculative Store Bypass" in which recent stores

			to the same memory location may not be observed by

			later loads during speculative execution. The idea

			is that such stores are unlikely and that they can

			be detected prior to instruction retirement at the

			end of a particular speculation execution window.

			In vulnerable processors, the speculatively forwarded

			store can be used in a cache side channel attack, for

			example to read memory to which the attacker does not

			directly have access (e.g. inside sandboxed code).

			This parameter controls whether the Speculative Store

			Bypass optimization is used.

			on      - Unconditionally disable Speculative Store Bypass

			off     - Unconditionally enable Speculative Store Bypass

			auto    - Kernel detects whether the CPU model contains an

				  implementation of Speculative Store Bypass and

				  picks the most appropriate mitigation. If the

				  CPU is not vulnerable, "off" is selected. If the

				  CPU is vulnerable the default mitigation is

				  architecture and Kconfig dependent. See below.

			prctl   - Control Speculative Store Bypass per thread

				  via prctl. Speculative Store Bypass is enabled

				  for a process by default. The state of the control

				  is inherited on fork.

			seccomp - Same as "prctl" above, but all seccomp threads

				  will disable SSB unless they explicitly opt out.

			Not specifying this option is equivalent to

			spec_store_bypass_disable=auto.

			Default mitigations:

			X86:	If CONFIG_SECCOMP=y "seccomp", otherwise "prctl"

	spia_io_base=	[HW,MTD]

	spia_fio_base=

	spia_pedr=

Memory region used to store USB PID and serial numbers to be used by

bootloader in download mode.

SSR Minidump Offset

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

-Compatible: "qcom,msm-imem-minidump"

-reg: start address and size of ssr imem region

Required properties:

-compatible: "qcom,msm-imem-diag-dload"

-reg: start address and size of USB Diag download mode region in imem

			compatible = "qcom,msm-imem-emergency_download_mode";

			reg = <0xfe0 12>;

		};

		ss_mdump@b88 {

			compatible = "qcom,msm-imem-minidump";

			reg = <0xb88 28>;

		};

	};

Memory offline driver

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

The memory offline driver supports the onlining and offlining of DDR memory.

Through the mem-offline node you can configure how much of the DDR will

support being offlined/onlined.

By default all memory is onlined when the device has booted up.

Note that offlinable memory can only support 'movable' memory allocations so

designating too much memory as offlinable can result in system performance and

stability issues.

For more information on how to request the onlining and offlining of memory

see the memory hotplug documentation (Documentation/memory-hotplug.txt).

Required properties:

- compatible: "qcom,mem-offline"

- granule: The minimum granule size in mega-bytes for memory onlining/offlining.

- mem-percent: Percentage of the DDR which will support being onlined/offlined.

	The system will round down the value to align with the minimum offlinable

	granule size supported by DDR.

- mboxes: Reference to the mailbox used by the driver to make requests to

	online/offline memory.

Example:

  mem-offline {

	compatible = "qcom,mem-offline";

	granule = <512>;

	mem-percent = "35";

	mboxes = <&qmp_aop 0>;

  };