drm/amdkfd: Update mapping if range attributes changed
authorPhilip Yang <Philip.Yang@amd.com>
Tue, 19 Apr 2022 01:38:43 +0000 (21:38 -0400)
committerAlex Deucher <alexander.deucher@amd.com>
Tue, 26 Apr 2022 15:42:59 +0000 (11:42 -0400)
commit601354f344334fe7ee98b71ee3391a8a4215a7f9
tree611bf084ee07662b95df85c130f9d59e7078f379
parent6b9c63a6eb540e678504a080865e9d3c716288ed
drm/amdkfd: Update mapping if range attributes changed

Change SVM range mapping flags or access attributes don't trigger
migration, if range is already mapped on GPUs we should update GPU
mapping and pass flush_tlb flag true to amdgpu vm.

Change SVM range preferred_loc or migration granularity don't need
update GPU mapping, skip the validate_and_map.

Signed-off-by: Philip Yang <Philip.Yang@amd.com>
Reviewed-by: Felix Kuehling <Felix.Kuehling@amd.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
drivers/gpu/drm/amd/amdkfd/kfd_svm.c