From: "Chen, Xiaogang" <xiaogang.chen@amd.com>
To: Felix Kuehling <felix.kuehling@amd.com>, amd-gfx@lists.freedesktop.org
Cc: philip.yang@amd.com
Subject: Re: [PATCH v2] drm/amdkfd: change kfd process kref count at creation
Date: Fri, 18 Oct 2024 17:02:11 -0500 [thread overview]
Message-ID: <9040368d-e698-4a3b-bf19-d7f3b35354b3@amd.com> (raw)
In-Reply-To: <f80e5f38-8235-4c73-89d1-c62991fe052d@amd.com>
On 10/18/2024 2:14 PM, Felix Kuehling wrote:
>
> On 2024-10-11 10:41, Xiaogang.Chen wrote:
>> From: Xiaogang Chen <xiaogang.chen@amd.com>
>>
>> kfd process kref count(process->ref) is initialized to 1 by
>> kref_init. After
>> it is created not need to increaes its kref. Instad add kfd process
>> kref at kfd
>> process mmu notifier allocation since we decrease the ref at
>> free_notifier of
>> mmu_notifier_ops, so pair them.
>>
>> When user process opens kfd node multiple times the kfd process kref is
>> increased each time to balance kfd node close operation.
>>
>> Signed-off-by: Xiaogang Chen <Xiaogang.Chen@amd.com>
>
> Thanks, this is an elegant solution, IMO. The reference returned by
> kfd_create_process comes either from find_process or create_process.
> And the extra reference that gets released by the free_notifier gets
> allocated by the alloc_notifier. I think there is a race condition,
> though. See inline.
>
>
>> ---
>> drivers/gpu/drm/amd/amdkfd/kfd_process.c | 15 ++++++++++-----
>> 1 file changed, 10 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>> b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>> index d07acf1b2f93..78bf918abf92 100644
>> --- a/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>> +++ b/drivers/gpu/drm/amd/amdkfd/kfd_process.c
>> @@ -850,8 +850,10 @@ struct kfd_process *kfd_create_process(struct
>> task_struct *thread)
>> goto out;
>> }
>> - /* A prior open of /dev/kfd could have already created the
>> process. */
>> - process = find_process(thread, false);
>> + /* A prior open of /dev/kfd could have already created the process.
>> + * find_process will increase process kref in this case
>> + */
>> + process = find_process(thread, true);
>> if (process) {
>> pr_debug("Process already found\n");
>> } else {
>> @@ -899,8 +901,6 @@ struct kfd_process *kfd_create_process(struct
>> task_struct *thread)
>> init_waitqueue_head(&process->wait_irq_drain);
>> }
>> out:
>> - if (!IS_ERR(process))
>> - kref_get(&process->ref);
>> mutex_unlock(&kfd_processes_mutex);
>> mmput(thread->mm);
>> @@ -1191,7 +1191,12 @@ static struct mmu_notifier
>> *kfd_process_alloc_notifier(struct mm_struct *mm)
>> srcu_read_unlock(&kfd_processes_srcu, idx);
>> - return p ? &p->mmu_notifier : ERR_PTR(-ESRCH);
>> + if (p) {
>> + kref_get(&p->ref);
>
> This should be inside the srcu. I think you could use
> kfd_lookup_process_by_mm instead of open-coding the SRCU locking and
> find_process_by_mm. This does the lookup and reference counting safely
> already.
>
ok, understand. Will do it after next week vacation.
Thanks
Xiaogang
> Regards,
> Felix
>
>> + return &p->mmu_notifier;
>> + }
>> +
>> + return ERR_PTR(-ESRCH);
>> }
>> static void kfd_process_free_notifier(struct mmu_notifier *mn)
prev parent reply other threads:[~2024-10-18 22:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 14:41 [PATCH v2] drm/amdkfd: change kfd process kref count at creation Xiaogang.Chen
2024-10-12 2:56 ` Zhu Lingshan
2024-10-12 17:30 ` Chen, Xiaogang
2024-10-14 1:55 ` Zhu Lingshan
2024-10-14 15:07 ` Chen, Xiaogang
2024-10-15 2:51 ` Zhu Lingshan
2024-10-15 4:49 ` Chen, Xiaogang
2024-10-18 19:14 ` Felix Kuehling
2024-10-18 22:02 ` Chen, Xiaogang [this message]
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=9040368d-e698-4a3b-bf19-d7f3b35354b3@amd.com \
--to=xiaogang.chen@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=felix.kuehling@amd.com \
--cc=philip.yang@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