All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Deng, Emily" <Emily.Deng-5C7GfCeVMHo@public.gmane.org>
To: "Zhou,
	David(ChunMing)" <David1.Zhou-5C7GfCeVMHo@public.gmane.org>,
	"amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
	<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: RE: [PATCH] drm/amdgpu: Fix the dead lock issue.
Date: Tue, 11 Sep 2018 03:23:26 +0000	[thread overview]
Message-ID: <BN7PR12MB2644CEE78E8E6D658D1A686E8F040@BN7PR12MB2644.namprd12.prod.outlook.com> (raw)
In-Reply-To: <bf049e4b-321f-33b4-dad2-708269515e90-5C7GfCeVMHo@public.gmane.org>

>-----Original Message-----
>From: Zhou, David(ChunMing)
>Sent: Tuesday, September 11, 2018 11:03 AM
>To: Deng, Emily <Emily.Deng@amd.com>; amd-gfx@lists.freedesktop.org
>Subject: Re: [PATCH] drm/amdgpu: Fix the dead lock issue.
>
>
>
>On 2018年09月11日 10:51, Emily Deng wrote:
>> It will ramdomly have the dead lock issue when test TDR:
>> 1. amdgpu_device_handle_vram_lost gets the lock shadow_list_lock 2.
>> amdgpu_bo_create locked the bo's resv lock 3. amdgpu_bo_create_shadow
>> is waiting for the shadow_list_lock 4.
>> amdgpu_device_recover_vram_from_shadow is waiting for the bo's resv
>> lock.
>>
>> v2:
>>     Make a local copy of the list
>>
>> Signed-off-by: Emily Deng <Emily.Deng@amd.com>
>> ---
>>   drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 21
>++++++++++++++++++++-
>>   1 file changed, 20 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> index 2a21267..8c81404 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_device.c
>> @@ -3105,6 +3105,9 @@ static int
>amdgpu_device_handle_vram_lost(struct amdgpu_device *adev)
>>   	long r = 1;
>>   	int i = 0;
>>   	long tmo;
>> +	struct list_head local_shadow_list;
>> +
>> +	INIT_LIST_HEAD(&local_shadow_list);
>>
>>   	if (amdgpu_sriov_runtime(adev))
>>   		tmo = msecs_to_jiffies(8000);
>> @@ -3112,8 +3115,19 @@ static int
>amdgpu_device_handle_vram_lost(struct amdgpu_device *adev)
>>   		tmo = msecs_to_jiffies(100);
>>
>>   	DRM_INFO("recover vram bo from shadow start\n");
>> +
>> +	mutex_lock(&adev->shadow_list_lock);
>> +	list_splice_init(&adev->shadow_list, &local_shadow_list);
>> +	mutex_unlock(&adev->shadow_list_lock);
>> +
>> +
>>   	mutex_lock(&adev->shadow_list_lock);
>local_shadow_list is a local variable, I think it doesn't need lock at all, no one
>change it. Otherwise looks good to me.
The bo->shadow_list which now is in local_shadow_list maybe destroy in case that it already in amdgpu_bo_destroy, then it will
change local_shadow_list, so need lock the shadow_list_lock.
Best wishes
Emily Deng
>Thanks,
>David Zhou
>> -	list_for_each_entry_safe(bo, tmp, &adev->shadow_list, shadow_list) {
>> +	list_for_each_entry_safe(bo, tmp, &local_shadow_list, shadow_list) {
>> +		mutex_unlock(&adev->shadow_list_lock);
>> +
>> +		if (!bo)
>> +			continue;
>> +
>>   		next = NULL;
>>   		amdgpu_device_recover_vram_from_shadow(adev, ring, bo,
>&next);
>>   		if (fence) {
>> @@ -3132,9 +3146,14 @@ static int
>> amdgpu_device_handle_vram_lost(struct amdgpu_device *adev)
>>
>>   		dma_fence_put(fence);
>>   		fence = next;
>> +		mutex_lock(&adev->shadow_list_lock);
>>   	}
>>   	mutex_unlock(&adev->shadow_list_lock);
>>
>> +	mutex_lock(&adev->shadow_list_lock);
>> +	list_splice_init(&local_shadow_list, &adev->shadow_list);
>> +	mutex_unlock(&adev->shadow_list_lock);
>> +
>>   	if (fence) {
>>   		r = dma_fence_wait_timeout(fence, false, tmo);
>>   		if (r == 0)

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

  parent reply	other threads:[~2018-09-11  3:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  2:51 [PATCH] drm/amdgpu: Fix the dead lock issue Emily Deng
     [not found] ` <1536634293-26099-1-git-send-email-Emily.Deng-5C7GfCeVMHo@public.gmane.org>
2018-09-11  3:01   ` Zhang, Jerry (Junwei)
2018-09-11  3:03   ` zhoucm1
     [not found]     ` <bf049e4b-321f-33b4-dad2-708269515e90-5C7GfCeVMHo@public.gmane.org>
2018-09-11  3:23       ` Deng, Emily [this message]
     [not found]         ` <BN7PR12MB2644CEE78E8E6D658D1A686E8F040-Zx/IyJUqfGKoYeSiBV3SvgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-09-11  3:27           ` zhoucm1
     [not found]             ` <fcbc7544-d08d-4051-c554-f1f9cecb87e1-5C7GfCeVMHo@public.gmane.org>
2018-09-11  3:32               ` Deng, Emily
     [not found]                 ` <BN7PR12MB2644E374B512DC7EF10CA6D08F040-Zx/IyJUqfGKoYeSiBV3SvgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-09-11  3:37                   ` zhoucm1
     [not found]                     ` <be67e50d-f161-c7da-256e-149ed1b56f26-5C7GfCeVMHo@public.gmane.org>
2018-09-11  5:41                       ` zhoucm1
     [not found]                         ` <83f7a45f-1aee-a2a8-bc82-f3433157c6cb-5C7GfCeVMHo@public.gmane.org>
2018-09-11  6:40                           ` Christian König
     [not found]                             ` <c67be83d-aecd-a291-a564-15f1fe501680-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-11  6:55                               ` Deng, Emily
  -- strict thread matches above, loose matches on Subject: below --
2018-09-10  4:07 Emily Deng
     [not found] ` <1536552453-18595-1-git-send-email-Emily.Deng-5C7GfCeVMHo@public.gmane.org>
2018-09-10  7:06   ` Christian König
     [not found]     ` <fe055a6c-0859-7404-6236-2c22eb8e3df5-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2018-09-10  7:19       ` Deng, Emily
     [not found]         ` <BN7PR12MB2644EBCEAD5A7EAD4700FDD28F050-Zx/IyJUqfGKoYeSiBV3SvgdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2018-09-10  7:23           ` Christian König
     [not found]             ` <6798b857-49ec-06b3-f25f-f9df91a1ae20-5C7GfCeVMHo@public.gmane.org>
2018-09-10  7:57               ` Deng, Emily

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=BN7PR12MB2644CEE78E8E6D658D1A686E8F040@BN7PR12MB2644.namprd12.prod.outlook.com \
    --to=emily.deng-5c7gfcevmho@public.gmane.org \
    --cc=David1.Zhou-5C7GfCeVMHo@public.gmane.org \
    --cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.