drm/amdgpu: Jpeg uses shard VM invalidation engine

Browse source

JPEG 5_0_2 has 2 instances per die. Each instance has 10 rings.
Each ring consuming a unique VM invalidation engine exhausts the
available engines per MMHUB.

All rings within a JPEG instance can safely share one engine since
MMHUB serializes concurrent invalidation requests via hardware
semaphore (see "drm/amdgpu: add invalidate semaphore support for
gmc v12.1").

Signed-off-by: Sonny Jiang <sonny.jiang@amd.com>
Acked-by: Leo Liu <leo.liu@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

...

This commit is contained in:

Sonny Jiang 2026-07-29 19:54:33 -04:00 • committed by Alex Deucher

parent f8ca2969ca

commit 5bdae605d0

3 changed files with 48 additions and 1 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

9

drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c

View file

38

drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.c

View file

2

drivers/gpu/drm/amd/amdgpu/amdgpu_jpeg.h

View file