Unverified Commit 02fce139 authored by Paul Burton's avatar Paul Burton
Browse files

Merge tag 'mips_fixes_5.4_3' into mips-next 



Pull in mips-fixes primarily to gain build fixes in order to allow
better testing of mips-next.

A few MIPS fixes:

- Fix VDSO time-related function behavior for systems where we need to
  fall back to syscalls, but were instead returning bogus results.

- A fix to TLB exception handlers for Cavium Octeon systems where they
  would inadvertently clobber the $1/$at register.

- A build fix for bcm63xx configurations.

- Switch to using my @kernel.org email address.

Signed-off-by: default avatarPaul Burton <paulburton@kernel.org>
parents 8a5a4998 b42aa3fd

.mailmap

+2 −1
Original line number Diff line number Diff line
@@ -196,7 +196,8 @@ Oleksij Rempel <linux@rempel-privat.de> <o.rempel@pengutronix.de> 
Oleksij Rempel <linux@rempel-privat.de> <ore@pengutronix.de>

Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>

Patrick Mochel <mochel@digitalimplant.org>

Paul Burton <paul.burton@mips.com> <paul.burton@imgtec.com>

Paul Burton <paulburton@kernel.org> <paul.burton@imgtec.com>

Paul Burton <paulburton@kernel.org> <paul.burton@mips.com>

Peter A Jonsson <pj@ludd.ltu.se>

Peter Oruba <peter@oruba.de>

Peter Oruba <peter.oruba@amd.com>

CREDITS

+4 −0
Original line number Diff line number Diff line
@@ -1637,6 +1637,10 @@ S: Panoramastrasse 18 
S: D-69126 Heidelberg

S: Germany



N: Simon Horman

M: horms@verge.net.au

D: Renesas ARM/ARM64 SoC maintainer



N: Christopher Horn

E: chorn@warwick.net

D: Miscellaneous sysctl hacks

Documentation/admin-guide/cgroup-v2.rst

+14 −6
Original line number Diff line number Diff line
@@ -615,8 +615,8 @@ on an IO device and is an example of this type. 
Protections

-----------



A cgroup is protected to be allocated upto the configured amount of

the resource if the usages of all its ancestors are under their

A cgroup is protected upto the configured amount of the resource

as long as the usages of all its ancestors are under their

protected levels.  Protections can be hard guarantees or best effort

soft boundaries.  Protections can also be over-committed in which case

only upto the amount available to the parent is protected among
@@ -1096,7 +1096,10 @@ PAGE_SIZE multiple when read back. 
	is within its effective min boundary, the cgroup's memory

	won't be reclaimed under any conditions. If there is no

	unprotected reclaimable memory available, OOM killer

	is invoked.

	is invoked. Above the effective min boundary (or

	effective low boundary if it is higher), pages are reclaimed

	proportionally to the overage, reducing reclaim pressure for

	smaller overages.



       Effective min boundary is limited by memory.min values of

	all ancestor cgroups. If there is memory.min overcommitment
@@ -1118,7 +1121,10 @@ PAGE_SIZE multiple when read back. 
	Best-effort memory protection.  If the memory usage of a

	cgroup is within its effective low boundary, the cgroup's

	memory won't be reclaimed unless memory can be reclaimed

	from unprotected cgroups.

	from unprotected cgroups.  Above the effective low boundary (or

	effective min boundary if it is higher), pages are reclaimed

	proportionally to the overage, reducing reclaim pressure for

	smaller overages.



	Effective low boundary is limited by memory.low values of

	all ancestor cgroups. If there is memory.low overcommitment
@@ -2482,8 +2488,10 @@ system performance due to overreclaim, to the point where the feature 
becomes self-defeating.



The memory.low boundary on the other hand is a top-down allocated

reserve.  A cgroup enjoys reclaim protection when it's within its low,

which makes delegation of subtrees possible.

reserve.  A cgroup enjoys reclaim protection when it's within its

effective low, which makes delegation of subtrees possible. It also

enjoys having reclaim pressure proportional to its overage when

above its effective low.



The original high boundary, the hard limit, is defined as a strict

limit that can not budge, even if the OOM killer has to be called.

Documentation/admin-guide/kernel-parameters.txt

+4 −0
Original line number Diff line number Diff line
@@ -5302,6 +5302,10 @@ 
				the unplug protocol

			never -- do not unplug even if version check succeeds



	xen_legacy_crash	[X86,XEN]

			Crash from Xen panic notifier, without executing late

			panic() code such as dumping handler.



	xen_nopvspin	[X86,XEN]

			Disables the ticketlock slowpath using Xen PV

			optimizations.

Documentation/arm64/memory.rst

+8 −1
Original line number Diff line number Diff line
@@ -154,11 +154,18 @@ return virtual addresses to userspace from a 48-bit range. 


Software can "opt-in" to receiving VAs from a 52-bit space by

specifying an mmap hint parameter that is larger than 48-bit.



For example:



.. code-block:: c



   maybe_high_address = mmap(~0UL, size, prot, flags,...);



It is also possible to build a debug kernel that returns addresses

from a 52-bit space by enabling the following kernel config options:



.. code-block:: sh



   CONFIG_EXPERT=y && CONFIG_ARM64_FORCE_52BIT=y



Note that this option is only intended for debugging applications

CRA Git | Maintained and supported by SUSTech CRA and CCSE