search for: uwind

...er the case where the NMI stack is > in-between, so I think you need to walk down regs->sp too. That shouldn't be possible with the current code, I think. > The dumpstack code already has some logic for this. Reliability of that depends on the unwinder, I wouldn't want the guess uwinder to OOPS me by accident.

...itive. I've written a program which should: 1. Recursively grow the stack until it reaches a threshold 2. Then unwind and print a message Instead what happens is: 1. Recursively grow the stack until it reaches a threshold 2. Then it dies with: Abort trap Can you point me to an example using uwind that "works" ? Thanks. Here's the code: %str_sp = internal constant [9 x sbyte] c"SP = %i\0A\00" ; <[9 x sbyte]*> [#uses=1] %str_msg = internal constant [15 x sbyte] c"Bottom'd Out!\0A\00" implementation ; Functions: declare int %printf(sbyte*, .....

...n before the NMI handler did the #VC stack check (because HV messed around with some pages touched there). In the second #VC you use the same IST stack as in the first #VC, but the the NMI-stack in-between. > Reliability of that depends on the unwinder, I wouldn't want the guess > uwinder to OOPS me by accident. It doesn't use the full unwinder, it just assumes that there is a pt_regs struct at the top of every kernel stack and walks through them until SP points to a user-space stack. As long as the assumption that there is a pt_regs struct on top of every stack holds, this...

On Tue, Jun 23, 2020 at 03:59:16PM +0200, Peter Zijlstra wrote: > So basically when your exception frame points to your own IST, you die. > That sounds like something we should have in generic IST code. Something like this... #DF already dies and NMI is 'magic' --- arch/x86/entry/common.c | 7 +++++++ arch/x86/include/asm/idtentry.h | 12 +++++++++++- 2 files changed, 18