Re: [PATCH] drm/ttm: stop always moving BOs on the LRU on page fault

2019-01-13 Thread zhoucm1
On 2019年01月11日 21:15, Christian König wrote: Move the BO on the LRU only when it is actually moved by a DMA operation. Signed-off-by: Christian König Tested-And-Reviewed-by: Chunming Zhou I just sent lru_notify  v2 patches, please review them. With yours and mine, the OOM issue is fixed

[PATCH 2/2] drm/amdgpu: set bulk_moveable to false when lru changed v2

2019-01-13 Thread Chunming Zhou
if lru is changed, we cannot do bulk moving. v2: root bo isn't bulk moving, skip its change. Change-Id: Ide0fe920295cc25f7cabcf41a6400519e5783f2a Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 3 ++- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 22

[PATCH 1/2] drm/ttm: add lru notify to bo driver v2

2019-01-13 Thread Chunming Zhou
allow driver do somethings when lru changed. v2: address Michel's comments. Change-Id: Ie82053da49272881d4b52b1c406f7c221a3fcadf Signed-off-by: Chunming Zhou --- drivers/gpu/drm/ttm/ttm_bo.c| 11 +++ include/drm/ttm/ttm_bo_driver.h | 9 + 2 files changed, 16 insertions(+),

radeon 0000:1d:00.0: GPU lockup (current fence id 0x00000000017a66bf last fence id 0x00000000017a67a1 on ring 0)

2019-01-13 Thread Borislav Petkov
Hi guys, my odyssey with the GPU continues. This time it didn't reset itself but started spewing a single line about the hardware locking up. The machine was responsive to sysrq so I was able to write out /var/log/messages and reboot. This is still with 4.20-rc7 but I'm building 5.0-rc1 to see

RE: [PATCH 1/3] drm/amdgpu: enable IH ring 1 and ring 2 v3

2019-01-13 Thread Kuehling, Felix
The series is Reviewed-by: Felix Kuehling -Original Message- From: Christian König Sent: Friday, January 11, 2019 7:02 AM To: amd-gfx@lists.freedesktop.org; Deucher, Alexander ; Kuehling, Felix Subject: Re: [PATCH 1/3] drm/amdgpu: enable IH ring 1 and ring 2 v3 Am 09.01.19 um 14:12

[PATCH] drm/amd/display: Include names of all PP clock types

2019-01-13 Thread Rafał Miłecki
From: Rafał Miłecki This fixes printing clock names in cases like: [5.352311] [drm] DM_PPLIB: values for Invalid clock [5.352313] [drm] DM_PPLIB: 40 in kHz [5.352313] [drm] DM_PPLIB: 933000 in kHz [5.352314] [drm] DM_PPLIB: 1067000 in kHz [5.352315] [drm] DM_PPLIB: