Commit 1b1d5c43 authored by Christian König's avatar Christian König Committed by Alex Deucher
Browse files

drm/amdgpu: use the maximum possible fragment size on Vega/Raven 



The fragment size controls only the L1 on Vega/Raven and we now don't
have any extra overhead any more because of larger fragments.

Signed-off-by: default avatarChristian König <christian.koenig@amd.com>
Reviewed-by: default avatarHuang Rui <ray.huang@amd.com>
Reviewed-by: default avatarFelix Kuehling <Felix.Kuehling@amd.com>
Acked-by: default avatarJunwei Zhang <Jerry.Zhang@amd.com>
Signed-off-by: default avatarAlex Deucher <alexander.deucher@amd.com>
parent dfcd99f6

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

+9 −1
Original line number Diff line number Diff line
@@ -1540,8 +1540,16 @@ static void amdgpu_vm_fragment(struct amdgpu_pte_update_params *params, 
	 * larger. Thus, we try to use large fragments wherever possible.

	 * Userspace can support this by aligning virtual base address and

	 * allocation size to the fragment size.

	 *

	 * Starting with Vega10 the fragment size only controls the L1. The L2

	 * is now directly feed with small/huge/giant pages from the walker.

	 */

	unsigned max_frag = params->adev->vm_manager.fragment_size;

	unsigned max_frag;



	if (params->adev->asic_type < CHIP_VEGA10)

		max_frag = params->adev->vm_manager.fragment_size;

	else

		max_frag = 31;



	/* system pages are non continuously */

	if (params->src || !(flags & AMDGPU_PTE_VALID)) {

CRA Git | Maintained and supported by SUSTech CRA and CCSE