diff options
| author | Vladimir Oltean <[email protected]> | 2021-10-24 20:17:57 +0300 |
|---|---|---|
| committer | David S. Miller <[email protected]> | 2021-10-25 12:59:42 +0100 |
| commit | eccd0a80dc7f4be65430236db475546b0ab9ec37 (patch) | |
| tree | ca7071763f0791120ec4ce1e5f0e03ea1c281e20 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | d70b51f2845d4a0352361fd4f9741913a2cf2145 (diff) | |
selftests: net: dsa: add a stress test for unlocked FDB operations
This test is a bit strange in that it is perhaps more manual than
others: it does not transmit a clear OK/FAIL verdict, because user space
does not have synchronous feedback from the kernel. If a hardware access
fails, it is in deferred context.
Nonetheless, on sja1105 I have used it successfully to find and solve a
concurrency issue, so it can be used as a starting point for other
driver maintainers too.
Signed-off-by: Vladimir Oltean <[email protected]>
Reviewed-by: Florian Fainelli <[email protected]>
Signed-off-by: David S. Miller <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions