summaryrefslogtreecommitdiffstats
path: root/net
diff options
context:
space:
mode:
authorBreno Leitao <leitao@debian.org>2018-09-12 17:31:05 -0300
committerMichael Ellerman <mpe@ellerman.id.au>2018-09-19 21:58:09 +1000
commit44d947eff19d64384efc06069509db7a0a1103b0 (patch)
treea47f2f6e70a66ff0d418b9864ac3fdfd953f8894 /net
parent984ecdd68de0fa1f63ce205d6c19ef5a7bc67b40 (diff)
downloadlinux-stable-44d947eff19d64384efc06069509db7a0a1103b0.tar.gz
linux-stable-44d947eff19d64384efc06069509db7a0a1103b0.tar.bz2
linux-stable-44d947eff19d64384efc06069509db7a0a1103b0.zip
selftests/powerpc: Do not fail with reschedule
There are cases where the test is not expecting to have the transaction aborted, but, the test process might have been rescheduled, either in the OS level or by KVM (if it is running on a KVM guest machine). The process reschedule will cause a treclaim/recheckpoint which will cause the transaction to doom, aborting the transaction as soon as the process is rescheduled back to the CPU. This might cause the test to fail, but this is not a failure in essence. If that is the case, TEXASR[FC] is indicated with either TM_CAUSE_RESCHEDULE or TM_CAUSE_KVM_RESCHEDULE for KVM interruptions. In this scenario, ignore these two failures and avoid the whole test to return failure. Signed-off-by: Breno Leitao <leitao@debian.org> Reviewed-by: Gustavo Romero <gromero@linux.ibm.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'net')
0 files changed, 0 insertions, 0 deletions