Go ahead with my RB.
-Original Message-
From: amd-gfx On Behalf Of Christian
K?nig
Sent: Monday, July 30, 2018 5:19 PM
To: amd-gfx@lists.freedesktop.org
Subject: [PATCH] drm/amdgpu: add new amdgpu_vm_bo_trace_cs() function v2
This allows us to trace all VM ranges which should be valid i
___
> From: amd-gfx on behalf of Huang Rui
>
> Sent: 29 July 2018 08:16:30
> To: Christian K?nig
> Cc: Grodzovsky, Andrey; amd-gfx@lists.freedesktop.org
> Subject: Re: [PATCH] drm/amdgpu: add new amdgpu_vm_bo_trace_cs() function
>
> On Fri, Jul 27, 2018 at 04:57:43PM +
Reviewed-by: Chunming Zhou
-Original Message-
From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of
Christian K?nig
Sent: Friday, July 27, 2018 10:58 PM
To: amd-gfx@lists.freedesktop.org; Grodzovsky, Andrey
Subject: [PATCH] drm/amdgpu: add new amdgpu_vm_bo_trace_cs
d-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/amdgpu: add new amdgpu_vm_bo_trace_cs() function
On Fri, Jul 27, 2018 at 04:57:43PM +0200, Christian König wrote:
> This allows us to trace all VM ranges which should be valid inside a CS.
>
> Signed-off-by: Christian König
Reviewed-by: Huang Rui
On Fri, Jul 27, 2018 at 04:57:43PM +0200, Christian König wrote:
> This allows us to trace all VM ranges which should be valid inside a CS.
>
> Signed-off-by: Christian König
Reviewed-by: Huang Rui
A bit curious, what kind of situation that we need trace all VM ranges
during the command submis
Reviewed-and-tested-by: Andrey Grodzovsky
Andrey
On 07/27/2018 10:57 AM, Christian König wrote:
This allows us to trace all VM ranges which should be valid inside a CS.
Signed-off-by: Christian König
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c| 2 ++
drivers/gpu/drm/amd/amdgpu/amdgpu
