diff options
| author | Lyude Paul <lyude@redhat.com> | 2026-09-17 14:54:28 -0400 |
|---|---|---|
| committer | Lyude Paul <lyude@redhat.com> | 2026-09-17 16:43:06 -0400 |
| commit | 82f4394bbe223fda560153257e5cf21bdb12b6a3 (patch) | |
| tree | 260b755a73933a1e54f019d36341697953701c12 /tools/perf/scripts/python | |
| parent | c7ef611a43bb3ab7e7738349a860418336d507db (diff) | |
| download | linux-next-82f4394bbe223fda560153257e5cf21bdb12b6a3.tar.gz linux-next-82f4394bbe223fda560153257e5cf21bdb12b6a3.zip | |
drm/nouveau/gsp/r570: Start saving comptag backing stores
One of the portions of OpenRM's fbsr process that we never implemented is
the saving and restoring of comptag backing stores. This isn't strictly
necessary for fbsr to work (as long as we don't specify bEnteringGcOff =
1), but implementing it brings us much closer to matching OpenRM's fbsr
process - which means we can rely on things being well tested on Nvidia's
side.
Now that we have the required driver workarounds in place and fetch the
required information from GSP's memsys on driver load, let's implement
support for this by fetching the required space for the compbit backing
stores and adding it to the amount of memory that we allocate for fbsr.
With this, we should be able to safely enable bEnteringGcOff in fbsr.
Signed-off-by: Lyude Paul <lyude@redhat.com>
Reviewed-by: Dave Airlie <airlied@redhat.com>
Link: https://patch.msgid.link/20260917185916.1089621-5-lyude@redhat.com
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions