Re: [PATCH v3] drm/amdkfd: Handle errors from svm validate and map

2023-09-20 Thread Philip Yang
On 2023-09-20 10:35, Felix Kuehling wrote: On 2023-09-20 10:20, Philip Yang wrote: On 2023-09-19 17:15, Felix Kuehling wrote: On 2023-09-19 10:21, Philip Yang wrote:

Re: [PATCH v3] drm/amdkfd: Handle errors from svm validate and map

2023-09-20 Thread Felix Kuehling
On 2023-09-20 10:20, Philip Yang wrote: On 2023-09-19 17:15, Felix Kuehling wrote: On 2023-09-19 10:21, Philip Yang wrote: If new range is splited to multiple pranges with max_svm_range_pages alignment and added to update_list, svm validate and map should keep going after error to make sur

Re: [PATCH v3] drm/amdkfd: Handle errors from svm validate and map

2023-09-20 Thread Philip Yang
On 2023-09-19 17:15, Felix Kuehling wrote: On 2023-09-19 10:21, Philip Yang wrote: If new range is splited to multiple pranges with max_svm_range_pages alignment and added to update_list, svm validate and map shoul

Re: [PATCH v3] drm/amdkfd: Handle errors from svm validate and map

2023-09-19 Thread Felix Kuehling
On 2023-09-19 10:21, Philip Yang wrote: If new range is splited to multiple pranges with max_svm_range_pages alignment and added to update_list, svm validate and map should keep going after error to make sure prange->mapped_to_gpu flag is up to date for the whole range. svm validate and map up

[PATCH v3] drm/amdkfd: Handle errors from svm validate and map

2023-09-19 Thread Philip Yang
If new range is splited to multiple pranges with max_svm_range_pages alignment and added to update_list, svm validate and map should keep going after error to make sure prange->mapped_to_gpu flag is up to date for the whole range. svm validate and map update set prange->mapped_to_gpu after mapping