Vitaly Kuznetsov b85c32dd27 selftests: kvm: report failed stage when exit reason is unexpected ...

When we get a report like

==== Test Assertion Failure ====
  x86_64/state_test.c:157: run->exit_reason == KVM_EXIT_IO
  pid=955 tid=955 - Success
     1	0x0000000000401350: main at state_test.c:154
     2	0x00007fc31c9e9412: ?? ??:0
     3	0x000000000040159d: _start at ??:?
  Unexpected exit reason: 8 (SHUTDOWN),

it is not obvious which particular stage failed. Add the info.

Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>

2018-12-21 11:28:21 +01:00

..

cr4_cpuid_sync_test.c

kvm: selftests: move arch-specific files to arch-specific locations

2018-10-17 00:26:16 +02:00

evmcs_test.c

selftests: kvm: report failed stage when exit reason is unexpected

2018-12-21 11:28:21 +01:00

hyperv_cpuid.c

KVM: selftests: Add hyperv_cpuid test

2018-12-14 17:59:56 +01:00

platform_info_test.c

kvm: selftests: move arch-specific files to arch-specific locations

2018-10-17 00:26:16 +02:00

set_sregs_test.c

kvm: selftests: move arch-specific files to arch-specific locations

2018-10-17 00:26:16 +02:00

state_test.c

selftests: kvm: report failed stage when exit reason is unexpected

2018-12-21 11:28:21 +01:00

sync_regs_test.c

kvm: selftests: move arch-specific files to arch-specific locations

2018-10-17 00:26:16 +02:00

vmx_tsc_adjust_test.c

KVM: selftests: state_test: test bare VMXON migration

2018-10-17 00:30:18 +02:00