linux/drivers/gpu/drm/amd/amdkfd, branch v5.7

device_cgroup: Cleanup cgroup eBPF device filter code

2020-04-13T18:41:54Z

Original cgroup v2 eBPF code for filtering device access made it possible to compile with CONFIG_CGROUP_DEVICE=n and still use the eBPF filtering. Change commit 4b7d4d453fc4 ("device_cgroup: Export devcgroup_check_permission") reverted this, making it required to set it to y. Since the device filtering (and all the docs) for cgroup v2 is no longer a "device controller" like it was in v1, someone might compile their kernel with CONFIG_CGROUP_DEVICE=n. Then (for linux 5.5+) the eBPF filter will not be invoked, and all processes will be allowed access to all devices, no matter what the eBPF filter says. Signed-off-by: Odin Ugedal Acked-by: Roman Gushchin Signed-off-by: Tejun Heo

drm/amdkfd: kfree the wrong pointer

2020-04-01T18:44:22Z

Originally, it kfrees the wrong pointer for mem_obj. It would cause memory leak under stress test. Signed-off-by: Jack Zhang Acked-by: Nirmoy Das Signed-off-by: Alex Deucher

drm: amd: fix spelling mistake "shoudn't" -> "shouldn't"

2020-03-19T04:03:05Z

There are spelling mistakes in pr_err messages and a comment. Fix these. Signed-off-by: Colin Ian King Signed-off-by: Alex Deucher

drm/amdkfd: Consolidate duplicated bo alloc flags

2020-03-10T19:54:34Z

ALLOC_MEM_FLAGS_* used are the same as the KFD_IOC_ALLOC_MEM_FLAGS_*, but they are interweavedly used in kernel driver, resulting in bad readability. For example, KFD_IOC_ALLOC_MEM_FLAGS_COHERENT is not referenced in kernel, and it functions implicitly in kernel through ALLOC_MEM_FLAGS_COHERENT, causing unnecessary confusion. Replace all occurrences of ALLOC_MEM_FLAGS_* with KFD_IOC_ALLOC_MEM_FLAGS_* to solve the problem. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Use pr_debug to print the message of reaching event limit

2020-03-10T19:54:27Z

People are inclined to think of the previous pr_warn message as an error, so use pre_debug instead. Signed-off-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Signal eviction fence on process destruction (v2)

2020-03-06T19:40:30Z

Otherwise BOs may wait for the fence indefinitely and never be destroyed. v2: Signal the fence right after destroying queues to avoid unnecessary delaye-delete in kfd_process_wq_release Signed-off-by: Felix Kuehling Reviewed-by: xinhui pan Acked-by: Christian König Signed-off-by: Alex Deucher

drm/amdkfd: Add more comments on GFX9 user CP queue MQD workaround

2020-03-06T19:34:30Z

Because too many things are involved in this workaround, we need more comments to avoid pitfalls. Signed-off-by: Yong Zhao Acked-by: Christian König Reviewed-by: Philip Yang Signed-off-by: Alex Deucher

drm/amdkfd: fix indentation issue

2020-03-05T05:26:45Z

There is a statement that is indented with spaces instead of a tab. Replace spaces with a tab. Signed-off-by: Colin Ian King Signed-off-by: Alex Deucher

drm/amdkfd: change SDMA MQD memory type

2020-02-28T21:59:20Z

SDMA MQD memory type is NC that causes MQD data overwritten accidentally by an old stable cache line. Changing it to UC default for GART will fix the issue. The mqd_gfx9 parameter is meant for control stacks that are allocated together with user mode queue MQDs. Setting mqd_gfx9 to true maps the control stack pages as NC. Here it was accidentally applied to SDMA MQDs, which are allocated together with the HIQ MQD. Setting the mqd_gfx9 to false avoids that. Signed-off-by: Eric Huang Acked-by: Yong Zhao Reviewed-by: Felix Kuehling Signed-off-by: Alex Deucher

drm/amdkfd: Make get_tile_config() generic

2020-02-28T21:59:20Z

Given we can query all the asic specific information from amdgpu_gfx_config, we can make get_tile_config() generic. Signed-off-by: Yong Zhao Reviewed-by: Alex Deucher Signed-off-by: Alex Deucher