Re: [PATCH] drm/amdgpu: Properly allocate VM invalidate engine

2017-11-14 Thread Christian König
Am 14.11.2017 um 03:30 schrieb Chunming Zhou: On 2017年11月14日 01:22, Christian König wrote: Am 13.11.2017 um 17:12 schrieb Oak Zeng: From: ozeng Properly allocate TLB invalidation engine to avoid conflict. The latest engine allocation on gfx9 is: Engine 0, 1: idle Engine 2, 3: firmware Engin

Re: [PATCH] drm/amdgpu: Properly allocate VM invalidate engine

2017-11-13 Thread Chunming Zhou
On 2017年11月14日 01:22, Christian König wrote: Am 13.11.2017 um 17:12 schrieb Oak Zeng: From: ozeng Properly allocate TLB invalidation engine to avoid conflict. The latest engine allocation on gfx9 is: Engine 0, 1: idle Engine 2, 3: firmware Engine 4~13: amdgpu ring, subject to change when rin

Re: [PATCH] drm/amdgpu: Properly allocate VM invalidate engine

2017-11-13 Thread Christian König
Am 13.11.2017 um 17:12 schrieb Oak Zeng: From: ozeng Properly allocate TLB invalidation engine to avoid conflict. The latest engine allocation on gfx9 is: Engine 0, 1: idle Engine 2, 3: firmware Engine 4~13: amdgpu ring, subject to change when ring number changes Engine 14~15: idle Engine 16: k

[PATCH] drm/amdgpu: Properly allocate VM invalidate engine

2017-11-13 Thread Oak Zeng
From: ozeng Properly allocate TLB invalidation engine to avoid conflict. The latest engine allocation on gfx9 is: Engine 0, 1: idle Engine 2, 3: firmware Engine 4~13: amdgpu ring, subject to change when ring number changes Engine 14~15: idle Engine 16: kfd tlb invalidation Engine 17: Gart flushes