AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Das, Nirmoy" <nirmoy.das@amd.com>
To: zhang <botton_zhang@163.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/1] drm/amdgpu: release gtt bo after each move test
Date: Wed, 13 Oct 2021 17:07:00 +0200	[thread overview]
Message-ID: <24b252fe-617b-c086-65eb-7e8ab69bf3a6@amd.com> (raw)
In-Reply-To: <80ecf91a-1ae3-50e8-df46-01c013a1eeb9@amd.com>

[-- Attachment #1: Type: text/plain, Size: 1807 bytes --]


On 10/13/2021 12:42 PM, Das, Nirmoy wrote:
>
>
> On 10/13/2021 3:22 AM, zhang wrote:
>>
>> Hi . Nirmoy
>>
>>
>> If you let continue to unpin. this will  allways test a same va for gtt
>>
>> I think we should  rafresh calculate the value n
>>
>
> Right, I guess then the test should only run till gart size.
>

Actually the test size calculation was fine, it is just that we wouldn't 
release BO after a successful test as the cleanup code is inside the 
test for loop.


Regards,

Nirmoy

>
> Regards,
>
> Nirmoy
>
>>
>> On 2021/10/12 20:10, Nirmoy Das wrote:
>>> When gart size is < gtt size this test will fail with
>>> -ENOMEM as we are not freeing gtt bo after each move test.
>>> This is generally not an issue when gart size >= gtt size.
>>>
>>> Reported-by: zhang<botton_zhang@163.com>
>>> Signed-off-by: Nirmoy Das<nirmoy.das@amd.com>
>>> ---
>>>   drivers/gpu/drm/amd/amdgpu/amdgpu_test.c | 2 +-
>>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_test.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_test.c
>>> index 909d830b513e..0cf2a560d673 100644
>>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_test.c
>>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_test.c
>>> @@ -212,7 +212,6 @@ static void amdgpu_do_test_moves(struct amdgpu_device *adev)
>>>   
>>>   		DRM_INFO("Tested GTT->VRAM and VRAM->GTT copy for GTT offset 0x%llx\n",
>>>   			 gart_addr - adev->gmc.gart_start);
>>> -		continue;
>>>   
>>>   out_lclean_unpin:
>>>   		amdgpu_bo_unpin(gtt_obj[i]);
>>> @@ -220,6 +219,7 @@ static void amdgpu_do_test_moves(struct amdgpu_device *adev)
>>>   		amdgpu_bo_unreserve(gtt_obj[i]);
>>>   out_lclean_unref:
>>>   		amdgpu_bo_unref(&gtt_obj[i]);
>>> +		continue;
>>>   out_lclean:
>>>   		for (--i; i >= 0; --i) {
>>>   			amdgpu_bo_unpin(gtt_obj[i]);

[-- Attachment #2: Type: text/html, Size: 3760 bytes --]

  reply	other threads:[~2021-10-13 15:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 12:10 [PATCH 1/1] drm/amdgpu: release gtt bo after each move test Nirmoy Das
     [not found] ` <2be293df-2656-c551-682e-b08955307c0b@163.com>
2021-10-13 10:42   ` Das, Nirmoy
2021-10-13 15:07     ` Das, Nirmoy [this message]
2021-10-13 15:04 ` Nirmoy Das
2021-10-13 15:10   ` Das, Nirmoy
2021-10-13 15:09 ` [PATCH 1/1] drm/amdgpu: fix BO leak after successful " Nirmoy Das
2021-10-20  8:50   ` Das, Nirmoy
2021-10-20 11:50   ` Christian König
2021-10-20 11:51     ` Christian König
2021-10-20 12:55       ` Das, Nirmoy
2021-10-21  6:58         ` Christian König
2021-10-21  2:07       ` zhang
2021-10-21  6:58         ` Christian König

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=24b252fe-617b-c086-65eb-7e8ab69bf3a6@amd.com \
    --to=nirmoy.das@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=botton_zhang@163.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox