aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
diff options
context:
space:
mode:
authorFelix Kuehling <[email protected]>2021-02-25 04:55:27 +0000
committerAlex Deucher <[email protected]>2021-04-21 01:50:14 +0000
commit564d2b92c7d4569cdc76a08fd700de1309faa5e8 (patch)
tree495b7e3d27701932131bbdf3bfff4d131c4c5f59 /drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c
parentdrm/amdkfd: refine migration policy with xnack on (diff)
downloadkernel-564d2b92c7d4569cdc76a08fd700de1309faa5e8.tar.gz
kernel-564d2b92c7d4569cdc76a08fd700de1309faa5e8.zip
drm/amdkfd: add svm range validate timestamp
With xnack on, add validate timestamp in order to handle GPU vm fault from multiple GPUs. If GPU retry fault need migrate the range to the best restore location, use range validate timestamp to record system timestamp after range is restored to update GPU page table. Because multiple pages of same range have multiple retry fault, define AMDGPU_SVM_RANGE_RETRY_FAULT_PENDING to the long time period that pending retry fault may still comes after page table update, to skip duplicate retry fault of same range. If difference between system timestamp and range last validate timestamp is bigger than AMDGPU_SVM_RANGE_RETRY_FAULT_PENDING, that means the retry fault is from another GPU, then continue to handle retry fault recover. Signed-off-by: Philip Yang <[email protected]> Reviewed-by: Felix Kuehling <[email protected]> Signed-off-by: Felix Kuehling <[email protected]> Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/amd/amdgpu/amdgpu_gart.c')
0 files changed, 0 insertions, 0 deletions