summaryrefslogtreecommitdiffstats
path: root/arch/arm64/kvm/regmap.c
diff options
context:
space:
mode:
authorJohn David Anglin <dave.anglin@bell.net>2014-04-27 16:20:47 -0400
committerHelge Deller <deller@gmx.de>2014-05-01 19:28:44 +0200
commite0d8898d76a785453bfaf6cd08b830a7d5189f78 (patch)
tree5b964adcc5e69f4874e1e45379b0754d1f0b6a82 /arch/arm64/kvm/regmap.c
parent455c6fdbd219161bd09b1165f11699d6d73de11c (diff)
downloadlinux-e0d8898d76a785453bfaf6cd08b830a7d5189f78.tar.bz2
parisc: remove _STK_LIM_MAX override
There are only a couple of architectures that override _STK_LIM_MAX to a non-infinity value. This changes the stack allocation semantics in subtle ways. For example, GNU make changes its stack allocation to the hard maximum defined by _STK_LIM_MAX. As a results, threads executed by processes running under make are allocated a stack size of _STK_LIM_MAX rather than a sensible default value. This causes various thread stress tests to fail when they can't muster more than about 50 threads. The attached change implements the default behavior used by the majority of architectures. Signed-off-by: John David Anglin <dave.anglin@bell.net> Reviewed-by: Carlos O'Donell <carlos@systemhalted.org> Cc: stable@vger.kernel.org # 3.14 Signed-off-by: Helge Deller <deller@gmx.de>
Diffstat (limited to 'arch/arm64/kvm/regmap.c')
0 files changed, 0 insertions, 0 deletions