AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
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
Subject: Re: [PATCH v2 1/2] drm/amdkfd: Fix false positive queue buffer free warning
Date: Wed, 15 Oct 2025 17:45:38 -0400	[thread overview]
Message-ID: <42c82bf6-e100-076f-18a6-43a50e758d8d@amd.com> (raw)
In-Reply-To: <682f9477-ae2c-4022-be84-620cb02e388a@amd.com>


On 2025-10-15 17:01, Chen, Xiaogang wrote:
>
> On 10/15/2025 3:11 PM, Philip Yang wrote:
>> Only show warning message if process mm is still alive when queue
>> buffer is freed to evcit the queues.
>>
>> If kfd_lookup_process_by_mm return NULL, means the process is already
>> exited and mm is gone, it is fine to free queue buffer.
>
> But another question is why a prange is still alive, its kfd process 
> is gone?
It is application process exited, kfd process structure still exist and 
available. The issue is race condition:

    do_exit
       exit_mmap
a.          mmu mm release notifier, schedule kfd release wq to destroy 
queue
              unmap_vmas
b.                mmu_notifier_range(.. MMU_NOTIFY_UNMAP...)

the step b is executed to unmap CWSR svm range, before step a kfd 
release wq destroy queue.


>
> When unmap a prange the queues that use it should have been stopped. 
> If not, there is problem somewhere. This warning message need be sent 
> no matter kfd process exists or not.
>
> I think a real problem here is kfd process need be alive as long as 
> any of its resource is still alive. In this case since prange is still 
> alive its kfd process should not be released(p should not be null). If 
> not we need wait all pranges from this process got released, then 
> release this kfd process.

kfd process structure is freed in kfd_process_wq_release after 
svm_range_list_fini.

Regards,

Philip

>
> Regards
>
> Xiaogang
>
>>
>> Fixes: b049504e211e ("drm/amdkfd: Validate user queue svm memory 
>> residency")
>> Signed-off-by: Philip Yang <Philip.Yang@amd.com>
>> ---
>>   drivers/gpu/drm/amd/amdkfd/kfd_svm.c | 5 +++--
>>   1 file changed, 3 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c 
>> b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
>> index 4d4a47313f5b..d1b2f8525f80 100644
>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_svm.c
>> @@ -2487,7 +2487,9 @@ svm_range_unmap_from_cpu(struct mm_struct *mm, 
>> struct svm_range *prange,
>>       bool unmap_parent;
>>       uint32_t i;
>>   -    if (atomic_read(&prange->queue_refcount)) {
>> +    p = kfd_lookup_process_by_mm(mm);
>> +
>> +    if (p && atomic_read(&prange->queue_refcount)) {
>>           int r;
>>             pr_warn("Freeing queue vital buffer 0x%lx, queue evicted\n",
>> @@ -2497,7 +2499,6 @@ svm_range_unmap_from_cpu(struct mm_struct *mm, 
>> struct svm_range *prange,
>>               pr_debug("failed %d to quiesce KFD queues\n", r);
>>       }
>>   -    p = kfd_lookup_process_by_mm(mm);
>>       if (!p)
>>           return;
>>       svms = &p->svms;

  reply	other threads:[~2025-10-15 21:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15 20:11 [PATCH v2 1/2] drm/amdkfd: Fix false positive queue buffer free warning Philip Yang
2025-10-15 20:11 ` [PATCH v2 2/2] drm/amdkfd: Stop user queues when process mm released Philip Yang
2025-10-15 20:40   ` Chen, Xiaogang
2025-10-15 21:33     ` Philip Yang
2025-10-16 14:46       ` Chen, Xiaogang
2025-10-17 22:34         ` Felix Kuehling
2025-10-17 22:43   ` Felix Kuehling
2025-10-20 14:26     ` Philip Yang
2025-10-15 21:01 ` [PATCH v2 1/2] drm/amdkfd: Fix false positive queue buffer free warning Chen, Xiaogang
2025-10-15 21:45   ` Philip Yang [this message]
2025-10-15 22:46     ` Chen, Xiaogang
2025-10-16 18:01       ` Philip Yang
2025-10-17 22:39       ` Felix Kuehling

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=42c82bf6-e100-076f-18a6-43a50e758d8d@amd.com \
    --to=yangp@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Philip.Yang@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox