Searched hist:"176 e1ab1" (Results 1 – 3 of 3) sorted by relevance
/openbmc/linux/drivers/gpu/drm/amd/amdgpu/ |
H A D | amdgpu_ring.c | 176e1ab1 Thu Jul 23 21:49:47 CDT 2015 Chunming Zhou <david1.zhou@amd.com> drm/amdgpu: protect fence_process from multiple context
fence_process may be called from kthread, user thread and interrupt context. it is possible to called concurrently, then will wake up fence queue multiple times.
Signed-off-by: Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Jammy Zhou <Jammy.Zhou@amd.com>
|
H A D | amdgpu_fence.c | 176e1ab1 Thu Jul 23 21:49:47 CDT 2015 Chunming Zhou <david1.zhou@amd.com> drm/amdgpu: protect fence_process from multiple context
fence_process may be called from kthread, user thread and interrupt context. it is possible to called concurrently, then will wake up fence queue multiple times.
Signed-off-by: Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Jammy Zhou <Jammy.Zhou@amd.com> 176e1ab1 Thu Jul 23 21:49:47 CDT 2015 Chunming Zhou <david1.zhou@amd.com> drm/amdgpu: protect fence_process from multiple context fence_process may be called from kthread, user thread and interrupt context. it is possible to called concurrently, then will wake up fence queue multiple times. Signed-off-by: Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Jammy Zhou <Jammy.Zhou@amd.com>
|
H A D | amdgpu.h | 176e1ab1 Thu Jul 23 21:49:47 CDT 2015 Chunming Zhou <david1.zhou@amd.com> drm/amdgpu: protect fence_process from multiple context
fence_process may be called from kthread, user thread and interrupt context. it is possible to called concurrently, then will wake up fence queue multiple times.
Signed-off-by: Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Jammy Zhou <Jammy.Zhou@amd.com> 176e1ab1 Thu Jul 23 21:49:47 CDT 2015 Chunming Zhou <david1.zhou@amd.com> drm/amdgpu: protect fence_process from multiple context fence_process may be called from kthread, user thread and interrupt context. it is possible to called concurrently, then will wake up fence queue multiple times. Signed-off-by: Chunming Zhou <david1.zhou@amd.com> Reviewed-by: Jammy Zhou <Jammy.Zhou@amd.com>
|