linux/arch/arc
Alexey Brodkin 8ff3afc159 ARC: Enable fatal signals on boot for dev platforms
It's very convenient to have fatal signals enabled on developemnt
platform as this allows to catch problems that happen early in
user-space (like crashing init or dynamic loader).

Otherwise we may either enable it later from alive taregt console
by "echo 1 > /proc/sys/kernel/print-fatal-signals" but:
 1. We might be unfortunate enough to not reach working console
 2. Forget to enable fatal signals and miss something interesting

Given we're talking about development platforms here it shouldn't
be a problem if a bit more data gets printed to debug console.

Moreover this makes behavior of all our dev platforms predictable
as today some platforms already have it enabled and some don't -
which is way too inconvenient.

Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
Signed-off-by: Vineet Gupta <vgupta@synopsys.com>
2018-01-18 10:51:27 -08:00
..
boot ARC: Enable fatal signals on boot for dev platforms 2018-01-18 10:51:27 -08:00
configs ARC: [plat-hsdk] Switch DisplayLink driver from fbdev to DRM 2017-12-20 12:41:43 -08:00
include ARCv2: Don't pretend we may set L-bit in STATUS32 with kflag instruction 2018-01-18 10:51:26 -08:00
kernel ARC: handle gcc generated __builtin_trap for older compiler 2018-01-03 00:31:27 -08:00
lib
mm ARCv2: cache: fix slc_entire_op: flush only instead of flush-n-inv 2018-01-17 12:26:52 -08:00
oprofile
plat-axs10x ARC: [plat-axs103] refactor the quad core DT quirk code 2017-12-20 12:41:45 -08:00
plat-eznps
plat-hsdk ARC: [plat-hsdk]: Get rid of core pll frequency set in platform code 2017-12-20 12:41:44 -08:00
plat-sim
plat-tb10x
Kbuild
Kconfig
Kconfig.debug
Makefile