summaryrefslogtreecommitdiffstats
path: root/arch/s390/lib/test_unwind.c
Commit message (Collapse)AuthorAgeFilesLines
* s390/test_unwind: fix spelling mistake "reqister" -> "register"Colin Ian King2019-12-111-1/+1
| | | | | | | | There is a spelling mistake in a pr_info message. Fix it. Link: https://lkml.kernel.org/r/20191202090215.28766-1-colin.king@canonical.com Signed-off-by: Colin Ian King <colin.king@canonical.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/test_unwind: add program check context testsVasily Gorbik2019-11-301-0/+47
| | | | | | | Add unwinding from program check handler tests. Unwinder should be able to unwind through pt_regs stored by program check handler on task stack. Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/test_unwind: add irq context testsVasily Gorbik2019-11-301-0/+45
| | | | | | | | Add unwinding from irq context tests. Unwinder should be able to unwind through irq stack to task stack up to task pt_regs. Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/test_unwind: print verbose unwinding resultsVasily Gorbik2019-11-301-2/+10
| | | | | | | | | Add stack name, sp and reliable information into test unwinding results. Also consider ip outside of kernel text as failure if the state is reported reliable. Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/test_unwind: add CALL_ON_STACK testsVasily Gorbik2019-11-301-7/+19
| | | | | | | | | | | | Add CALL_ON_STACK helper testing. Tests make sure that we can unwind from switched stack to original one up to task pt_regs (nodat -> task stack). UWM_SWITCH_STACK could not be used together with UWM_THREAD because get_stack_info explicitly restricts unwinding to task stack if task != current. Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/test_unwind: require that unwinding ended successfullyVasily Gorbik2019-11-301-0/+4
| | | | | | | | | | Currently unwinder test passes if unwinding results contain unwindme_func2 and unwindme_func1 functions. Now that unwinder reports success upon reaching task pt_regs, check that unwinding ended successfully in every test. Acked-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
* s390/unwind: add a test for the internal APIIlya Leoshkevich2019-11-301-0/+231
unwind_for_each_frame can take at least 8 different sets of parameters. Add a test to make sure they all are handled in a sane way. Reviewed-by: Heiko Carstens <heiko.carstens@de.ibm.com> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com> Co-developed-by: Vasily Gorbik <gor@linux.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com>
OpenPOWER on IntegriCloud