diff options
| author |   Nicholas Piggin <npiggin@gmail.com> | 2016-12-20 04:30:05 +1000 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2017-04-28 21:02:25 +1000 |
| commit | c4f3b52ce7b16824befb16ab3d045c891b08b7db (patch) | |
| tree | 92f77ba25144dbe046368583e18e21c83015e642 /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | powerpc/64s: Fix system reset vs general interrupt reentrancy (diff) | |
| download | wireguard-linux-c4f3b52ce7b16824befb16ab3d045c891b08b7db.tar.xz wireguard-linux-c4f3b52ce7b16824befb16ab3d045c891b08b7db.zip | |
powerpc/64s: Disallow system reset vs system reset reentrancy
In preparation for using a dedicated stack for system reset interrupts,
prevent a nested system reset from recovering, in order to simplify
code that is called in crash/debug path. This allows a system reset
interrupt to just use the base stack pointer.
Keep an in_nmi nesting counter similarly to the in_mce counter. Consider
the interrrupt non-recoverable if it is taken inside another system
reset.
Interrupt nesting could be allowed similarly to MCE, but system reset
is a special case that's not for normal operation, so simplicity wins
until there is requirement for nested system reset interrupts.
Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions