diff options
| author | Matthew Brost <matthew.brost@intel.com> | 2025-10-08 14:45:05 -0700 |
|---|---|---|
| committer | Matthew Brost <matthew.brost@intel.com> | 2025-10-09 03:22:22 -0700 |
| commit | 0ca229da92bf29b59410d9fae77e5f304df6ab6b (patch) | |
| tree | 8338a26152518cd09e134fbf1682f951171d51a9 /tools/perf/scripts/python/bin/stackcollapse-record | |
| parent | 807c42dd8028d71222dfce035c2e87aaecbf623f (diff) | |
| download | linux-0ca229da92bf29b59410d9fae77e5f304df6ab6b.tar.gz linux-0ca229da92bf29b59410d9fae77e5f304df6ab6b.zip | |
drm/xe: Make LRC W/A scratch buffer usage consistent
The LRC W/A currently checks for LRC being iomem in some places, while
in others it checks if the scratch buffer is non-NULL. This
inconsistency causes issues with the VF post-migration recovery code,
which blindly passes in a scratch buffer.
This patch standardizes the check by consistently verifying whether the
LRC is iomem to determine if the scratch buffer should be used.
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Tomasz Lis <tomasz.lis@intel.com>
Reviewed-by: Lucas De Marchi <lucas.demarchi@intel.com>
Link: https://lore.kernel.org/r/20251008214532.3442967-8-matthew.brost@intel.com
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions