From: "Khatri, Sunil" <sukhatri@amd.com>
To: Alex Deucher <alexdeucher@gmail.com>,
Sunil Khatri <sunil.khatri@amd.com>
Cc: "Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org
Subject: Re: [PATCH v1] drm/amdgpu/userq: change queue id type to u32 from int
Date: Thu, 26 Feb 2026 20:35:18 +0530 [thread overview]
Message-ID: <5b409ab7-7c63-4020-8d96-461cb649ecaf@amd.com> (raw)
In-Reply-To: <CADnq5_M7B++68+Kgo7Eb+y-mco=P9Ov4JT=2HkrubFNYxRVBVw@mail.gmail.com>
On 26-02-2026 08:30 pm, Alex Deucher wrote:
> On Thu, Feb 26, 2026 at 2:42 AM Sunil Khatri <sunil.khatri@amd.com> wrote:
>> queue id always remain a positive value and should
>> be of type unsigned.
> Does it need to be a u32 or can you just use an unsigned int?
UAPI, where we are returning the queue id is u32 and based on that i
changed this to u32 only, but i guess unsigned int also should be ok.
whatever you suggest is fine for me.
Regards
Sunil khatri
>
> Alex
>
>> With this we also dont need to typecast the id to other
>> types specially in xarray functions.
>>
>> Signed-off-by: Sunil Khatri <sunil.khatri@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c | 8 ++++----
>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c
>> index b700c2b91465..e07b2082cf25 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_userq.c
>> @@ -447,7 +447,7 @@ static int amdgpu_userq_wait_for_last_fence(struct amdgpu_usermode_queue *queue)
>> }
>>
>> static void amdgpu_userq_cleanup(struct amdgpu_usermode_queue *queue,
>> - int queue_id)
>> + u32 queue_id)
>> {
>> struct amdgpu_userq_mgr *uq_mgr = queue->userq_mgr;
>> struct amdgpu_device *adev = uq_mgr->adev;
>> @@ -461,7 +461,7 @@ static void amdgpu_userq_cleanup(struct amdgpu_usermode_queue *queue,
>> uq_funcs->mqd_destroy(queue);
>> amdgpu_userq_fence_driver_free(queue);
>> /* Use interrupt-safe locking since IRQ handlers may access these XArrays */
>> - xa_erase_irq(&uq_mgr->userq_xa, (unsigned long)queue_id);
>> + xa_erase_irq(&uq_mgr->userq_xa, queue_id);
>> xa_erase_irq(&adev->userq_doorbell_xa, queue->doorbell_index);
>> queue->userq_mgr = NULL;
>> list_del(&queue->userq_va_list);
>> @@ -471,7 +471,7 @@ static void amdgpu_userq_cleanup(struct amdgpu_usermode_queue *queue,
>> }
>>
>> static struct amdgpu_usermode_queue *
>> -amdgpu_userq_find(struct amdgpu_userq_mgr *uq_mgr, int qid)
>> +amdgpu_userq_find(struct amdgpu_userq_mgr *uq_mgr, u32 qid)
>> {
>> return xa_load(&uq_mgr->userq_xa, qid);
>> }
>> @@ -625,7 +625,7 @@ amdgpu_userq_get_doorbell_index(struct amdgpu_userq_mgr *uq_mgr,
>> }
>>
>> static int
>> -amdgpu_userq_destroy(struct drm_file *filp, int queue_id)
>> +amdgpu_userq_destroy(struct drm_file *filp, u32 queue_id)
>> {
>> struct amdgpu_fpriv *fpriv = filp->driver_priv;
>> struct amdgpu_userq_mgr *uq_mgr = &fpriv->userq_mgr;
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2026-02-26 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 7:42 [PATCH v1] drm/amdgpu/userq: change queue id type to u32 from int Sunil Khatri
2026-02-26 15:00 ` Alex Deucher
2026-02-26 15:05 ` Khatri, Sunil [this message]
2026-02-26 16:09 ` Alex Deucher
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=5b409ab7-7c63-4020-8d96-461cb649ecaf@amd.com \
--to=sukhatri@amd.com \
--cc=alexander.deucher@amd.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=sunil.khatri@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