From: Philip Yang <yangp@amd.com>
To: "Chen, Xiaogang" <xiaogang.chen@amd.com>,
Philip Yang <Philip.Yang@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: Felix.Kuehling@amd.com, christian.koenig@amd.com
Subject: Re: [PATCH 3/3] drm/amdkfd: destroy_pdds release pdd->drm_file at end
Date: Fri, 16 May 2025 09:07:24 -0400 [thread overview]
Message-ID: <162ba0d2-6b5d-5199-f560-b3eb4fc6fd29@amd.com> (raw)
In-Reply-To: <8966fa75-4c46-45c0-b9c6-543f8d10f340@amd.com>
On 2025-05-15 17:31, Chen, Xiaogang wrote:
>
> On 5/15/2025 3:45 PM, Philip Yang wrote:
>>
>> On 2025-05-15 10:29, Chen, Xiaogang wrote:
>>>
>>> Does this patch fix a bug or just make code look more reasonable?
>>> kfd_process_destroy_pdds releases pdd related buffers, not related
>>> to operations on vm. So vm tear down dose not affect this function.
>>>
>> This change doesn't fix anything currently, as fput(pdd->drm_file) to
>> free vm is right between free vm mapping qpd->cwsr_mem, qpd->ib_mem
>> and free kernel bo qpd->proc_doorbells, pdd->proc_ctx_bo, to make it
>> clear for future change.
>
> Then the current place to do fput(pdd->drm_file) make more sense:
> unmap vm mapping of qpd->cwsr_mem, qpd->ib_mem is the last place where
> kfd process release procedure needs vm alive. After that the kfd
> process release does not need vm alive. It then releases remaining
> buffers. So release drm_file as soon as we do not need hold it.
The issue was vm_fini shows error message "still active bo inside vm"
(1/1000) chance, took a while to trace down the leaking vm mapping, the
issue is seq64 memory mapping leaking and fixed by the first patch. KFD
pdd cleanup path, free vm is in the middle of free pdd memory, this is
one of the suspicious vm_fini race. We may add new pdd memory mapping to
vm in future, to prevent the potential vm_fini race, this patch move
free vm to after all pdd memory is freed and add comment.
Regards,
Philip
>
> Regards
>
> Xiaogang
>
>> Regards,
>>
>> Philip
>>
>>> Regards
>>>
>>> Xiaogang
>>>
>>> On 5/14/2025 12:10 PM, Philip Yang wrote:
>>>> Release pdd->drm_file may free the vm if this is the last reference,
>>>> move it to the last step after memory is unmapped.
>>>>
>>>> Signed-off-by: Philip Yang<Philip.Yang@amd.com>
>>>> ---
>>>> drivers/gpu/drm/amd/amdkfd/kfd_process.c | 10 +++++++---
>>>> 1 file changed, 7 insertions(+), 3 deletions(-)
>>>>
>>>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>>> b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>>> index e868cc8da46f..b009c852180d 100644
>>>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>>>> @@ -1063,9 +1063,6 @@ static void kfd_process_destroy_pdds(struct
>>>> kfd_process *p)
>>>> kfd_process_device_destroy_cwsr_dgpu(pdd);
>>>> kfd_process_device_destroy_ib_mem(pdd);
>>>> - if (pdd->drm_file)
>>>> - fput(pdd->drm_file);
>>>> -
>>>> if (pdd->qpd.cwsr_kaddr && !pdd->qpd.cwsr_base)
>>>> free_pages((unsigned long)pdd->qpd.cwsr_kaddr,
>>>> get_order(KFD_CWSR_TBA_TMA_SIZE));
>>>> @@ -1088,6 +1085,13 @@ static void kfd_process_destroy_pdds(struct
>>>> kfd_process *p)
>>>> pdd->runtime_inuse = false;
>>>> }
>>>> + /*
>>>> + * This may release the vm if application already close
>>>> the drm node,
>>>> + * do it as last step after memory unmapped.
>>>> + */
>>>> + if (pdd->drm_file)
>>>> + fput(pdd->drm_file);
>>>> +
>>>> kfree(pdd);
>>>> p->pdds[i] = NULL;
>>>> }
next prev parent reply other threads:[~2025-05-16 13:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 17:10 [PATCH 0/3] Remove process exit error message Philip Yang
2025-05-14 17:10 ` [PATCH 1/3] drm/amdgpu: seq64 memory unmap uses uninterruptible lock Philip Yang
2025-05-21 7:06 ` Christian König
2025-05-14 17:10 ` [PATCH 2/3] drm/amdgpu: amdgpu_vm_fini hold vm lock to access vm->va Philip Yang
2025-05-15 12:18 ` Christian König
2025-05-15 14:40 ` Chen, Xiaogang
2025-05-15 19:47 ` Philip Yang
2025-05-14 17:10 ` [PATCH 3/3] drm/amdkfd: destroy_pdds release pdd->drm_file at end Philip Yang
2025-05-15 14:29 ` Chen, Xiaogang
2025-05-15 20:45 ` Philip Yang
2025-05-15 21:31 ` Chen, Xiaogang
2025-05-16 13:07 ` Philip Yang [this message]
2025-05-16 15:19 ` Chen, Xiaogang
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=162ba0d2-6b5d-5199-f560-b3eb4fc6fd29@amd.com \
--to=yangp@amd.com \
--cc=Felix.Kuehling@amd.com \
--cc=Philip.Yang@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=xiaogang.chen@amd.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 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.