From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
To: Felix Kuehling <felix.kuehling@amd.com>,
Tvrtko Ursulin <tursulin@igalia.com>,
amd-gfx@lists.freedesktop.org
Cc: "Christian König" <christian.koenig@amd.com>, kernel-dev@igalia.com
Subject: Re: [PATCH 3/3] drm/amdgpu: Fix pinned GART area accounting and fdinfo reporting
Date: Mon, 29 Apr 2024 10:43:11 +0100 [thread overview]
Message-ID: <fe80a8db-3ece-4818-8b23-2ccf5293a6c2@igalia.com> (raw)
In-Reply-To: <a60dede1-8e81-4c79-8058-257391930621@amd.com>
On 26/04/2024 23:24, Felix Kuehling wrote:
>
> On 2024-04-26 12:43, Tvrtko Ursulin wrote:
>> From: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
>>
>> When commit b453e42a6e8b ("drm/amdgpu: Add new placement for preemptible
>> SG BOs") added a new TTM region it missed to notice the conceptual
>> imbalance in GART pin size accounting as done in amdgpu_bo_pin/unpin.
>>
>> That imbalance leads to such objects getting accounted against the
>> resource, but are not un-accounted when unpinned.
>
> AMDGPU_PL_PREEMPT is mostly used for userptr BOs, which cannot be
> pinned. In any case you should make sure that the accounting is
> consistent between amdgpu_bo_pin_restricted and amdgpu_bo_unpin. This
> patch breaks that consistency.
You mean amdgpu_bo_pin(_restricted) and amdgpu_bo_unpin do not run for
such objects, or something else?
If they run, then at the end of pin there is:
domain = amdgpu_mem_type_to_domain(bo->tbo.resource->mem_type);
...
} else if (domain == AMDGPU_GEM_DOMAIN_GTT) {
atomic64_add(amdgpu_bo_size(bo), &adev->gart_pin_size);
And unpin has no handling for AMDGPU_PL_PREEMPT.
Ah I see.. does it rely on amdgpu_mem_type_to_domain returning 0 for
AMDGPU_PL_PREEMPT? My confusion was I misread the pinning check as
checking the domain as stored in the bo at creation time.
Although I am still confused by the statement userptr BOs are not
pinned. It is not needed to map them via GART on AMD hardware for GPU to
be able to access them?
>> Fix by extending the accounting criteria in amdgpu_bo_unpin.
>>
>> What also aappears needs fixing is not reporting their size from the
>> amdgpu_bo_get_memory, which is used to implement fdinfo stats, so they
>> are
>> not mixed with the regular userspace created and driver owned objects.
>
> I think that's true. It's a very fine distinction. AMDGPU_PL_PREEMPT
> does use system memory and it is GPU accessible, just like GTT. The only
> difference is, that it's not subject to the GTT limits because their
> eviction is handled by callbacks other than TTM evictions and doesn't
> need to wait for fences.
As in you think those two hunks of the patch are correct?
Regards,
Tvrtko
> Regards,
> Felix
>
>
>>
>> And also amdgpu_bo_print_info for debugfs reporting.
>>
>> Note that the patch depends on the previous one which broke down the
>> relevant checks from the domain based to placement based.
>>
>> Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@igalia.com>
>> Fixes: b453e42a6e8b ("drm/amdgpu: Add new placement for preemptible SG
>> BOs")
>> Cc: Felix Kuehling <Felix.Kuehling@amd.com>
>> Cc: Christian König <christian.koenig@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 5 ++---
>> 1 file changed, 2 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> index fb984669fc3a..5a2bbc793953 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.c
>> @@ -1032,7 +1032,8 @@ void amdgpu_bo_unpin(struct amdgpu_bo *bo)
>> atomic64_sub(amdgpu_bo_size(bo), &adev->vram_pin_size);
>> atomic64_sub(amdgpu_vram_mgr_bo_visible_size(bo),
>> &adev->visible_pin_size);
>> - } else if (bo->tbo.resource->mem_type == TTM_PL_TT) {
>> + } else if (bo->tbo.resource->mem_type == TTM_PL_TT ||
>> + bo->tbo.resource->mem_type == AMDGPU_PL_PREEMPT) {
>> atomic64_sub(amdgpu_bo_size(bo), &adev->gart_pin_size);
>> }
>> @@ -1298,7 +1299,6 @@ void amdgpu_bo_get_memory(struct amdgpu_bo *bo,
>> stats->vram_shared += size;
>> break;
>> case TTM_PL_TT:
>> - case AMDGPU_PL_PREEMPT:
>> stats->gtt += size;
>> if (shared)
>> stats->gtt_shared += size;
>> @@ -1599,7 +1599,6 @@ u64 amdgpu_bo_print_info(int id, struct
>> amdgpu_bo *bo, struct seq_file *m)
>> placement = "VRAM";
>> break;
>> case TTM_PL_TT:
>> - case AMDGPU_PL_PREEMPT:
>> placement = "GTT";
>> break;
>> case TTM_PL_SYSTEM:
next prev parent reply other threads:[~2024-04-29 13:05 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-26 16:43 [PATCH 0/3] Some refactoring and maybe a memory accounting fixlet Tvrtko Ursulin
2024-04-26 16:43 ` [PATCH 1/3] drm/amdgpu: Add amdgpu_bo_is_vm_bo helper Tvrtko Ursulin
2024-04-29 11:02 ` Christian König
2024-04-29 13:34 ` Tvrtko Ursulin
2024-04-29 13:51 ` Christian König
2024-04-26 16:43 ` [PATCH 2/3] drm/amdgpu: Reduce mem_type to domain double indirection Tvrtko Ursulin
2024-04-29 11:03 ` Christian König
2024-04-29 13:38 ` Tvrtko Ursulin
2024-04-26 16:43 ` [PATCH 3/3] drm/amdgpu: Fix pinned GART area accounting and fdinfo reporting Tvrtko Ursulin
2024-04-26 22:24 ` Felix Kuehling
2024-04-29 9:43 ` Tvrtko Ursulin [this message]
2024-04-29 11:11 ` Christian König
2024-04-29 13:45 ` Tvrtko Ursulin
2024-04-29 14:34 ` Felix Kuehling
2024-04-29 14:43 ` Felix Kuehling
2024-04-29 16:51 ` Tvrtko Ursulin
2024-04-29 11:06 ` 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=fe80a8db-3ece-4818-8b23-2ccf5293a6c2@igalia.com \
--to=tvrtko.ursulin@igalia.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=felix.kuehling@amd.com \
--cc=kernel-dev@igalia.com \
--cc=tursulin@igalia.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