diff options
| author | Alexey Brodkin <abrodkin@synopsys.com> | 2018-01-18 14:48:47 +0100 |
|---|---|---|
| committer | Vineet Gupta <vgupta@synopsys.com> | 2018-01-18 19:51:27 +0100 |
| commit | 8ff3afc159f26e44471e174077e6d16cd2a2bb91 (patch) | |
| tree | 61073b3f16a48c6c6caf8c51fbe7549e2d38dbbb /init | |
| parent | ARCv2: Don't pretend we may set L-bit in STATUS32 with kflag instruction (diff) | |
| download | linux-8ff3afc159f26e44471e174077e6d16cd2a2bb91.tar.xz linux-8ff3afc159f26e44471e174077e6d16cd2a2bb91.zip | |
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>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions