diff options
| author | Boris Brezillon <boris.brezillon@collabora.com> | 2026-09-24 14:30:45 +0200 |
|---|---|---|
| committer | Liviu Dudau <liviu.dudau@arm.com> | 2026-10-16 13:20:46 +0100 |
| commit | 9a96e169c9267af918d28fb291df948d83112807 (patch) | |
| tree | d450c09cd6ba67bef5f9f5de2350d9279ebaac4d /scripts/stackusage | |
| parent | a431d4ec5d938893060f69a018a2c47651c282d9 (diff) | |
| download | linux-9a96e169c9267af918d28fb291df948d83112807.tar.gz linux-9a96e169c9267af918d28fb291df948d83112807.zip | |
drm/panthor: Move cache-flush after UPDATE(UNMAPPED)
Right now, there's a theoretical window during which the GPU can populate
the cache with data from a VM that's about to be evicted through the
UPDATE(UNMAPPED) command.
In practice this won't happen (hence the absence of Fixes tag) because
when panthor_mmu_as_disable() is called, the VM is guaranteed to be idle
(no active CSG pointing to this VM), but as we say, better safe than
sorry.
Signed-off-by: Boris Brezillon <boris.brezillon@collabora.com>
Signed-off-by: Liviu Dudau <liviu.dudau@arm.com>
Link: https://patch.msgid.link/20260924-panthor-mmu-fixes-v1-3-e25f9b106466@collabora.com
Diffstat (limited to 'scripts/stackusage')
0 files changed, 0 insertions, 0 deletions