Searched hist:fda8158870063b99b88a0904bbb95188973b4297 (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/tools/testing/selftests/powerpc/dscr/ |
| H A D | dscr_explicit_test.c | diff fda8158870063b99b88a0904bbb95188973b4297 Wed Apr 05 23:33:17 CDT 2023 Benjamin Gray <bgray@linux.ibm.com> selftests/powerpc/dscr: Add lockstep test cases to DSCR explicit tests
Add new cases to the relevant tests that use explicitly synchronized
threads to test the behaviour across context switches with less
randomness. By locking the participants to the same CPU we guarantee a
context switch occurs each time they make progress, which is a likely
failure point if the kernel is not tracking the thread local DSCR
correctly.
The random case is left in to keep exercising potential edge cases.
Signed-off-by: Benjamin Gray <bgray@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230406043320.125138-5-bgray@linux.ibm.com
|
| H A D | dscr_default_test.c | diff fda8158870063b99b88a0904bbb95188973b4297 Wed Apr 05 23:33:17 CDT 2023 Benjamin Gray <bgray@linux.ibm.com> selftests/powerpc/dscr: Add lockstep test cases to DSCR explicit tests
Add new cases to the relevant tests that use explicitly synchronized
threads to test the behaviour across context switches with less
randomness. By locking the participants to the same CPU we guarantee a
context switch occurs each time they make progress, which is a likely
failure point if the kernel is not tracking the thread local DSCR
correctly.
The random case is left in to keep exercising potential edge cases.
Signed-off-by: Benjamin Gray <bgray@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230406043320.125138-5-bgray@linux.ibm.com
|
| H A D | Makefile | diff fda8158870063b99b88a0904bbb95188973b4297 Wed Apr 05 23:33:17 CDT 2023 Benjamin Gray <bgray@linux.ibm.com> selftests/powerpc/dscr: Add lockstep test cases to DSCR explicit tests
Add new cases to the relevant tests that use explicitly synchronized
threads to test the behaviour across context switches with less
randomness. By locking the participants to the same CPU we guarantee a
context switch occurs each time they make progress, which is a likely
failure point if the kernel is not tracking the thread local DSCR
correctly.
The random case is left in to keep exercising potential edge cases.
Signed-off-by: Benjamin Gray <bgray@linux.ibm.com>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://msgid.link/20230406043320.125138-5-bgray@linux.ibm.com
|