diff options
| author | Jordan Niethe <jniethe5@gmail.com> | 2021-02-08 14:29:57 +1100 |
|---|---|---|
| committer | Michael Ellerman <mpe@ellerman.id.au> | 2021-04-08 21:17:42 +1000 |
| commit | 29e3ea8cbd2958cf237b84652ec236803f2c6202 (patch) | |
| tree | e1aa74b82d820142cb383a99e332b814016bfbd2 /tools/perf/scripts/python | |
| parent | powerpc/64s: Fix pte update for kernel memory on radix (diff) | |
| download | linux-29e3ea8cbd2958cf237b84652ec236803f2c6202.tar.gz linux-29e3ea8cbd2958cf237b84652ec236803f2c6202.zip | |
selftests/powerpc: Test for spurious kernel memory faults on radix
Previously when mapping kernel memory on radix, no ptesync was
included which would periodically lead to unhandled spurious faults.
Mapping kernel memory is used when code patching with Strict RWX
enabled. As suggested by Chris Riedl, turning ftrace on and off does a
large amount of code patching so is a convenient way to see this kind
of fault.
Add a selftest to try and trigger this kind of a spurious fault. It
tests for 30 seconds which is usually long enough for the issue to
show up.
Signed-off-by: Jordan Niethe <jniethe5@gmail.com>
[mpe: Rename it to better reflect what it does, rather than the symptom]
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20210208032957.1232102-2-jniethe5@gmail.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions