drm/amdgpu: Let KFD use more VMIDs on Aldebaran

When there is no graphics support, KFD can use more of the VMIDs. Graphics
VMIDs are only used for video decoding/encoding and post processing. With
two VCE engines, there is no reason to reserve more than 2 VMIDs for that.

Signed-off-by: Felix Kuehling <Felix.Kuehling@amd.com>
Reviewed-by: Alex Deucher <alexander.deucher@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
index 00c8ec80f19eb17df2c3682372b86762ca920bc8..45ba3819bb8fcb90bfceb0d204b2f5d5d4efa8d6 100644 (file)
--- a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c
@@ -1559,7 +1559,8 @@ static int gmc_v9_0_sw_init(void *handle)
         * for video processing.
         */
        adev->vm_manager.first_kfd_vmid =
-               adev->asic_type == CHIP_ARCTURUS ? 3 : 8;
+               (adev->asic_type == CHIP_ARCTURUS ||
+                adev->asic_type == CHIP_ALDEBARAN) ? 3 : 8;
 
        amdgpu_vm_manager_init(adev);