From: Felix Kuehling Date: Wed, 10 Feb 2021 02:26:14 +0000 (-0500) Subject: drm/amdgpu: Let KFD use more VMIDs on Aldebaran X-Git-Url: http://git.maquefel.me/?a=commitdiff_plain;h=6dce50b1aae0777ea1f1b631e390fe9ca68b4aeb;p=linux.git 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 Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher --- diff --git a/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c b/drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c index 00c8ec80f19eb..45ba3819bb8fc 100644 --- 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);