diff options
| author | Dave Airlie <airlied@redhat.com> | 2026-06-15 14:47:37 +1000 |
|---|---|---|
| committer | Danilo Krummrich <dakr@kernel.org> | 2026-06-21 16:05:36 +0200 |
| commit | d008141ed4ce924167a03d46fbce9ad1fe4efa29 (patch) | |
| tree | bafec9033faa69d1938714adb070a1ed081733aa /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 5e17160d41d92823f3379c1982e1369680c5ce4d (diff) | |
nouveau/vmm: fix another SPT/LPT race
We've had an unknown Turing issue for a while with page faults since
large pages and compression.
I've got a patch series that syncs all our L2 handling with ogkm and it
made this fault happen more.
After writing a bunch of debugging patches, I spotted an invalid LPT
entry where there should have been a valid one.
A 64K MAP succeeds on a range, but a subsequent SPT put drops SPT refs
across multiple ranges,
We shouldn't assume all ranges where SPTEs go away will have the same
sparse/invalid/valid state, just iterate over each instead and do the
right thing.
Cc: stable@vger.kernel.org
Signed-off-by: Dave Airlie <airlied@redhat.com>
Fixes: d19512f5abb1 ("nouveau/vmm: start tracking if the LPT PTE is valid. (v6)")
Link: https://patch.msgid.link/20260615044737.3419585-1-airlied@gmail.com
[ Properly format commit message. - Danilo ]
Signed-off-by: Danilo Krummrich <dakr@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions
