diff options
| author | Michael Ellerman <mpe@ellerman.id.au> | 2018-05-02 15:07:26 +0200 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2018-06-03 12:43:42 +0200 |
| commit | 7b08729cb272b4cd5c657cd5ac0dddae15a593ff (patch) | |
| tree | c6f727c760e0bc39cf30aae936b5aa0f63ada55d /scripts | |
| parent | powerpc: Check address limit on user-mode return (TIF_FSCHECK) (diff) | |
| download | linux-7b08729cb272b4cd5c657cd5ac0dddae15a593ff.tar.xz linux-7b08729cb272b4cd5c657cd5ac0dddae15a593ff.zip | |
powerpc/64: Save stack pointer when we hard disable interrupts
A CPU that gets stuck with interrupts hard disable can be difficult to
debug, as on some platforms we have no way to interrupt the CPU to
find out what it's doing.
A stop-gap is to have the CPU save it's stack pointer (r1) in its paca
when it hard disables interrupts. That way if we can't interrupt it,
we can at least trace the stack based on where it last disabled
interrupts.
In some cases that will be total junk, but the stack trace code should
handle that. In the simple case of a CPU that disable interrupts and
then gets stuck in a loop, the stack trace should be informative.
We could clear the saved stack pointer when we enable interrupts, but
that loses information which could be useful if we have nothing else
to go on.
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions