James Hogan c70458f50c metag: Remove _STK_LIM_MAX override ... Meta overrode _STK_LIM_MAX (the default RLIMIT_STACK hard limit) to 256MB, apparently in an attempt to prevent setup_arg_pages's STACK_GROWSUP code from choosing the maximum stack size of 1GB, which is far too large for Meta's limited virtual address space and hits a BUG_ON (stack_top is usually 0x3ffff000). However the commit "metag: Reduce maximum stack size to 256MB" reduces the absolute stack size limit to a safe value for metag. This allows the default _STK_LIM_MAX override to be removed, bringing the default behaviour in line with all other architectures. Parisc in particular recently removed their override of _STK_LIMT_MAX in commit e0d8898d76 (parisc: remove _STK_LIM_MAX override) since it subtly affects stack allocation semantics in userland. Meta's uapi/asm/resource.h can now be removed and switch to using generic-y. Suggested-by: Helge Deller <deller@gmx.de> Signed-off-by: James Hogan <james.hogan@imgtec.com> Cc: linux-metag@vger.kernel.org Cc: John David Anglin <dave.anglin@bell.net>		2014-05-15 00:30:32 +01:00
..
boot
configs
include	metag: Remove _STK_LIM_MAX override	2014-05-15 00:30:32 +01:00
kernel	Most of the changes were largely clean ups, and some documentation.	2014-04-03 10:26:31 -07:00
lib
mm	memblock: make memblock_set_node() support different memblock_type	2014-01-21 16:19:44 -08:00
oprofile
tbx	metag: handle low level kicks directly	2013-11-06 10:40:02 +00:00
Kconfig	Kconfig: rename HAS_IOPORT to HAS_IOPORT_MAP	2014-04-07 16:36:11 -07:00
Kconfig.debug
Kconfig.soc
Makefile