From: Shashank Sharma <shashank.sharma@amd.com>
To: "Christian König" <christian.koenig@amd.com>,
amd-gfx@lists.freedesktop.org
Cc: Alex Deucher <alexander.deucher@amd.com>,
pierre-eric.pelloux-prayer@amd.com,
contactshashanksharma@gmail.com, arvind.yadav@amd.com
Subject: Re: [PATCH v4 09/10] drm/amdgpu: generate doorbell index for userqueue
Date: Tue, 25 Apr 2023 15:34:13 +0200 [thread overview]
Message-ID: <2468fcbb-2f4c-56fc-585b-11d5d6f65c91@amd.com> (raw)
In-Reply-To: <44d081c1-8bd3-53ba-a60b-0fd6fe630aa0@amd.com>
On 25/04/2023 14:38, Christian König wrote:
> Am 24.04.23 um 19:38 schrieb Shashank Sharma:
>> The userspace sends us the doorbell object and the doobell index
>> to be used for the usermode queue, but the FW expects the absolute
>> doorbell index on the PCI BAR in the MQD. This patch adds a function
>> to convert this relative doorbell index to the absolute doorbell index.
>>
>> This patch is dependent on the doorbell manager series being reviewed
>> here: https://patchwork.freedesktop.org/series/115802/
>>
>> Cc: Alex Deucher <alexander.deucher@amd.com>
>> Cc: Christian Koenig <christian.koenig@amd.com>
>> Signed-off-by: Shashank Sharma <shashank.sharma@amd.com>
>> ---
>> drivers/gpu/drm/amd/amdgpu/amdgpu_userqueue.c | 33 +++++++++++++++++++
>> 1 file changed, 33 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_userqueue.c
>> b/drivers/gpu/drm/amd/amdgpu/amdgpu_userqueue.c
>> index 385cd51b6c96..fbc9cb5c24ad 100644
>> --- a/drivers/gpu/drm/amd/amdgpu/amdgpu_userqueue.c
>> +++ b/drivers/gpu/drm/amd/amdgpu/amdgpu_userqueue.c
>> @@ -44,6 +44,30 @@ amdgpu_userqueue_find(struct amdgpu_userq_mgr
>> *uq_mgr, int qid)
>> return idr_find(&uq_mgr->userq_idr, qid);
>> }
>> +static uint64_t
>> +amdgpu_userqueue_get_doorbell_index(struct amdgpu_userq_mgr *uq_mgr,
>> + struct amdgpu_usermode_queue *queue,
>> + struct drm_file *filp,
>> + uint32_t doorbell_index)
>> +{
>> + struct drm_gem_object *gobj;
>> + struct amdgpu_bo *db_bo;
>> + uint64_t index;
>> +
>> + gobj = drm_gem_object_lookup(filp, queue->doorbell_handle);
>> + if (gobj == NULL) {
>> + DRM_ERROR("Can't find GEM object for doorbell\n");
>> + return -EINVAL;
>> + }
>> +
>> + db_bo = amdgpu_bo_ref(gem_to_amdgpu_bo(gobj));
>
> That looks like we are leaking the object reference here.
>
That's correct, I will fix it.
- Shashank
> Christian.
>
>> + drm_gem_object_put(gobj);
>> +
>> + index = amdgpu_doorbell_index_on_bar(uq_mgr->adev, db_bo,
>> doorbell_index);
>> + DRM_DEBUG_DRIVER("[Usermode queues] doorbell index=%lld\n", index);
>> + return index;
>> +}
>> +
>> static int
>> amdgpu_userqueue_map_gtt_bo_to_gart(struct amdgpu_device *adev,
>> struct amdgpu_bo *bo)
>> {
>> @@ -133,6 +157,7 @@ static int amdgpu_userqueue_create_gfx(struct
>> drm_file *filp, union drm_amdgpu_u
>> struct amdgpu_fpriv *fpriv = filp->driver_priv;
>> struct amdgpu_userq_mgr *uq_mgr = &fpriv->userq_mgr;
>> struct drm_amdgpu_userq_mqd_gfx *mqd_in = &args->in.mqd.gfx;
>> + uint64_t index;
>> int r;
>> /* Do we support usermode queues on this GFX IP ? */
>> @@ -154,6 +179,14 @@ static int amdgpu_userqueue_create_gfx(struct
>> drm_file *filp, union drm_amdgpu_u
>> queue->userq_prop.hqd_base_gpu_addr = mqd_in->queue_va;
>> queue->doorbell_handle = mqd_in->doorbell_handle;
>> + index = amdgpu_userqueue_get_doorbell_index(uq_mgr, queue, filp,
>> mqd_in->doorbell_offset);
>> + if (index == (uint64_t)-EINVAL) {
>> + DRM_ERROR("Invalid doorbell object\n");
>> + r = -EINVAL;
>> + goto free_queue;
>> + }
>> +
>> + queue->userq_prop.doorbell_index = index;
>> queue->queue_type = AMDGPU_HW_IP_GFX;
>> queue->flags = mqd_in->flags;
>> queue->vm = &fpriv->vm;
>
next prev parent reply other threads:[~2023-04-25 13:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 17:38 [PATCH v4 00/10] AMDGPU usermode queues Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 01/10] drm/amdgpu: UAPI for user queue management Shashank Sharma
2023-05-19 21:03 ` Alex Deucher
2023-05-22 8:54 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 02/10] drm/amdgpu: add usermode queue base code Shashank Sharma
2023-04-25 12:03 ` Christian König
2023-04-25 12:19 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 03/10] drm/amdgpu: add new IOCTL for usermode queue Shashank Sharma
2023-04-25 12:14 ` Christian König
2023-04-25 12:21 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 04/10] drm/amdgpu: create GFX-gen11 MQD for userqueue Shashank Sharma
2023-04-25 12:27 ` Christian König
2023-04-25 13:10 ` Shashank Sharma
2023-04-25 13:45 ` Christian König
2023-04-25 17:02 ` Shashank Sharma
2023-05-19 21:19 ` Alex Deucher
2023-05-22 9:05 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 05/10] drm/amdgpu: create context space for usermode queue Shashank Sharma
2023-04-25 12:30 ` Christian König
2023-04-25 13:13 ` Shashank Sharma
2023-04-25 17:38 ` Deucher, Alexander
2023-04-25 20:00 ` Sharma, Shashank
2023-05-19 21:21 ` Alex Deucher
2023-05-22 9:05 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 06/10] drm/amdgpu: set FW parameters in v11_struct Shashank Sharma
2023-04-25 12:32 ` Christian König
2023-04-25 13:27 ` Shashank Sharma
2023-05-19 21:22 ` Alex Deucher
2023-05-22 9:06 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 07/10] drm/amdgpu: map usermode queue into MES Shashank Sharma
2023-04-25 12:34 ` Christian König
2023-04-25 13:31 ` Shashank Sharma
2023-04-25 15:33 ` Christian König
2023-04-25 16:56 ` Shashank Sharma
2023-05-19 21:22 ` Alex Deucher
2023-05-22 9:06 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 08/10] drm/amdgpu: map wptr BO into GART Shashank Sharma
2023-04-25 12:36 ` Christian König
2023-04-25 13:33 ` Shashank Sharma
2023-04-24 17:38 ` [PATCH v4 09/10] drm/amdgpu: generate doorbell index for userqueue Shashank Sharma
2023-04-25 12:38 ` Christian König
2023-04-25 13:34 ` Shashank Sharma [this message]
2023-04-24 17:38 ` [PATCH v4 10/10] drm/amdgpu: cleanup leftover queues Shashank Sharma
2023-04-25 12:40 ` Christian König
2023-04-25 13:34 ` Shashank Sharma
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=2468fcbb-2f4c-56fc-585b-11d5d6f65c91@amd.com \
--to=shashank.sharma@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=arvind.yadav@amd.com \
--cc=christian.koenig@amd.com \
--cc=contactshashanksharma@gmail.com \
--cc=pierre-eric.pelloux-prayer@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