AMD-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Chen, Xiaogang" <xiaogang.chen@amd.com>
To: Philip Yang <Philip.Yang@amd.com>, amd-gfx@lists.freedesktop.org
Cc: Felix.Kuehling@amd.com
Subject: Re: [PATCH v3 1/2] drm/amdkfd: Fix false positive queue buffer free warning
Date: Mon, 20 Oct 2025 10:59:30 -0500	[thread overview]
Message-ID: <f82491c6-c6f5-449e-89e1-1735606f60d0@amd.com> (raw)
In-Reply-To: <20251020143016.23409-1-Philip.Yang@amd.com>

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


On 10/20/2025 9:30 AM, Philip Yang wrote:
> Only show warning message if process mm is still alive when queue
> buffer is freed.
>
> 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.
>
> 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);

p->mm is null, not p  because driver set p->mm to null. But still 
prange->queue_refcount is ref of queues from this prange. If app unmap 
this prange app should have destroyed the queues associated with this 
prange already. If not, it is not driver issue. I think driver should 
send this warning anyway to indicate there are queues not destroyed by 
app before app unmap the prange. It is an app race condition, not driver.

Regards

Xiaogang

> +
> +	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;

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

  parent reply	other threads:[~2025-10-20 15:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-20 14:30 [PATCH v3 1/2] drm/amdkfd: Fix false positive queue buffer free warning Philip Yang
2025-10-20 14:30 ` [PATCH v3 2/2] drm/amdkfd: Dequeue user queues when process mm released Philip Yang
2025-10-20 15:59 ` Chen, Xiaogang [this message]
2025-10-20 16:24   ` [PATCH v3 1/2] drm/amdkfd: Fix false positive queue buffer free warning Kim, Jonathan
2025-10-20 17:33     ` Chen, Xiaogang
2025-10-20 17:45       ` Kim, Jonathan
2025-10-20 17:51         ` Chen, Xiaogang
2025-10-20 16:34   ` Philip Yang
2025-10-20 17:29     ` Chen, Xiaogang
2025-10-22 18:13       ` Philip Yang

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=f82491c6-c6f5-449e-89e1-1735606f60d0@amd.com \
    --to=xiaogang.chen@amd.com \
    --cc=Felix.Kuehling@amd.com \
    --cc=Philip.Yang@amd.com \
    --cc=amd-gfx@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox