linux/drivers/gpu/drm/amd/amdkfd/kfd_kernel_queue.c, branch v5.8

drm/amdkfd: Enable over-subscription with >1 GWS queue

2020-04-28T20:20:30Z

The current GWS usage model will only allows a single GWS-enabled process to be active on the GPU at once. This ensures that a barrier-using kernel gets a known amount of GPU hardware, to prevent deadlock due to inability to go beyond the GWS barrier. The HWS watches how many GWS entries are assigned to each process, and goes into over-subscription mode when two processes need more than the 64 that are available. The current KFD method for working with this is to allocate all 64 GWS entries to each GWS-capable process. When more than one GWS-enabled process is in the runlist, we must make sure the runlist is in over-subscription mode, so that the HWS gets a chained RUN_LIST packet and continues scheduling kernels. Signed-off-by: Joseph Greathouse Reviewed-by: Felix Kuehling Signed-off-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Avoid hanging hardware in stop_cpsch

2020-01-07T16:55:04Z

Don't use the HWS if it's known to be hanging. In a reset also don't try to destroy the HIQ because that may hang on SRIOV if the KIQ is unresponsive. Signed-off-by: Felix Kuehling Tested-by: Emily Deng Reviewed-by: shaoyunl Signed-off-by: Alex Deucher

drm/amdkfd: Eliminate unnecessary kernel queue function pointers

2019-12-05T21:24:36Z

Up to this point, those functions are all the same for all ASICs, so no need to call them by functions pointers. Removing the function pointers will greatly increase the code readablity. If there is ever need for those function pointers, we can add it back then. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Eliminate ops_asic_specific in kernel queue

2019-11-19T14:47:17Z

The ops_asic_specific function pointers are actually quite generic after using a simple if condition. Eliminate it by code refactoring. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Merge CIK kernel queue functions into VI

2019-11-19T14:47:02Z

The only difference that CIK kernel queue functions are different from VI is avoid allocating eop_mem. We can achieve that by using a if condition. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Use kernel queue v9 functions for v10

2019-11-13T20:29:45Z

The kernel queue functions for v9 and v10 are the same except pm_map_process_v* which have small difference, so they should be reused. This eliminates the need of reapplying several patches which were applied on v9 but not on v10, such as bigger GWS and more than 2 SDMA engine support which were introduced on Arcturus. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: use navi12 specific family id for navi12 code path

2019-10-03T14:11:03Z

Keep the same use of CHIP_IDs for navi12 in kfd Signed-off-by: shaoyunl Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher

drm/amdkfd: init kernel queue for renoir

2019-09-16T14:55:21Z

Renoir is GFX v9, so init v9 kernel queue. Signed-off-by: Huang Rui Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Support Navi14 in KFD

2019-09-16T14:54:40Z

Initial support of Navi14 in KFD. The device IDs will be added later. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

amd/amdkfd: Add ASIC ARCTURUS to kfd

2019-07-18T19:18:03Z

Add initial support for ARCTURUS to kfd. Signed-off-by: Yong Zhao Signed-off-by: Oak Zeng Signed-off-by: Alex Deucher