RE: [PATCH] amdgpu_device_recover_vram always failed if only one node in shadow_list

2019-04-03 Thread Lou, Wentao
Hi Christian, Sometimes shadow->parent would be NULL in my testbed, but not reproduce today... Just sent out another patch following your advice. Thanks. BR, Wentao -Original Message- From: Christian König Sent: Tuesday, April 2, 2019 6:36 PM To: Lou, Wentao ; amd-

RE: [PATCH] drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list

2019-04-02 Thread Lou, Wentao
Thanks Christian. You mean msecs_to_jiffies(8000) should be time to complete whole loop, not each loop. Just sent out another patch for review. Thanks. BR, Wentao -Original Message- From: Koenig, Christian Sent: Tuesday, April 2, 2019 3:39 PM To: Lou, Wentao ; Deng, Emily ; amd-gfx

RE: [PATCH] drm/amdgpu: amdgpu_device_recover_vram always failed if only one node in shadow_list

2019-04-02 Thread Lou, Wentao
ght pass a different value of tmo into dma_fence_wait_timeout. BR, Wentao -Original Message- From: Christian König Sent: Tuesday, April 2, 2019 3:01 PM To: Deng, Emily ; Lou, Wentao ; amd-gfx@lists.freedesktop.org Subject: Re: [PATCH] drm/amdgpu: amdgpu_device_recover_vram always fail

RE: [PATCH] drm/amdgpu: tighten gpu_recover in mailbox_flr to avoid duplicate recover in sriov

2019-01-23 Thread Lou, Wentao
by xgpu_ai_mailbox_flr_work would make vk-cts failed. -Original Message- From: Grodzovsky, Andrey Sent: Thursday, January 24, 2019 12:27 AM To: Lou, Wentao ; amd-gfx@lists.freedesktop.org Subject: Re: [PATCH] drm/amdgpu: tighten gpu_recover in mailbox_flr to avoid duplicate recover in sriov On 01

RE: [PATCH] drm/amdgpu: csa_vaddr should not larger than AMDGPU_GMC_HOLE_START

2019-01-17 Thread Lou, Wentao
a problem then there is a bug somewhere else.” 0x FFF0 should be inside the hole, so why it is a correct address? Much thanks. BR, Wentao From: Koenig, Christian Sent: Thursday, January 17, 2019 4:30 PM To: Liu, Monk ; Lou, Wentao ; amd-gfx@lists.freedesktop.org; Zhu, Rex Cc: Deng, Emily

RE: [PATCH] drm/amdgpu: csa_vaddr should not larger than AMDGPU_GMC_HOLE_START

2019-01-16 Thread Lou, Wentao
efore commit 1bf621c42137926ac249af761c0190a9258aa0db, vm_size was 32GB, and csa_addr was under AMDGPU_GMC_HOLE_START. I didn’t understand why csa_addr need to be above AMDGPU_GMC_HOLE_START now. Thanks. BR, Wentao From: Koenig, Christian Sent: Wednesday, January 16, 2019 5:48 PM To: Lou,

RE: [PATCH] drm/amdgpu: csa_vaddr should not larger than AMDGPU_GMC_HOLE_START

2019-01-16 Thread Lou, Wentao
anuary 15, 2019 4:02 PM To: Liu, Monk ; Lou, Wentao ; amd-gfx@lists.freedesktop.org; Zhu, Rex Subject: Re: [PATCH] drm/amdgpu: csa_vaddr should not larger than AMDGPU_GMC_HOLE_START Am 15.01.19 um 07:19 schrieb Liu, Monk: > The max_pfn is now 1'''' (bytes) which is above 4

RE: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback

2018-12-25 Thread Lou, Wentao
, Wentao -Original Message- From: Grodzovsky, Andrey Sent: Saturday, December 22, 2018 12:57 AM To: Lou, Wentao ; amd-gfx@lists.freedesktop.org Subject: Re: [PATCH] drm/amdgpu: dma_fence finished signaled by unexpected callback I believe this issue would be resolved by my pending

RE: [PATCH] drm/amdgpu: kfd_pre_reset outside req_full_gpu cause sriov hang

2018-12-10 Thread Lou, Wentao
(adev))" based on branch amd-staging-dkms-4.18. BR, Wentao -Original Message- From: Liu, Shaoyun Sent: Tuesday, December 11, 2018 12:10 AM To: Lou, Wentao ; amd-gfx@lists.freedesktop.org; Grodzovsky, Andrey ; Kuehling, Felix Cc: Lou, Wentao Subject: RE: [PATCH] drm/amdgpu: kfd