From: Shashank Sharma <shashank.sharma@amd.com>
To: <amd-gfx@lists.freedesktop.org>
Cc: alexander.deucher@amd.com,
Shashank Sharma <contactshashanksharma@gmail.com>,
christian.koenig@amd.com, Arvind.Yadav@amd.com,
shashank.sharma@amd.com
Subject: [PATCH v2 0/8] Re-design doorbell framework for usermode queues
Date: Tue, 14 Feb 2023 17:15:02 +0100 [thread overview]
Message-ID: <20230214161510.2153-1-shashank.sharma@amd.com> (raw)
From: Shashank Sharma <contactshashanksharma@gmail.com>
This patch series re-designs the current doorbell handling of the AMDGPU
driver and prepares it for Usermode queues. The fundamental changes are:
- Introduce and accommodate a new GEM domain for doorbells.
- Prepare the AMDGPU ttm backend for handling doorbell memory.
- Create a doorbell BO for kernel-level doorbell opertations.
- Rename, move and re-arrange some existing structures.
The idea is that a usermode app can directly allocate a page from
the doorbell bar and use it's offsets for different usermode queues.
Corresponding libdrm changes (just addition of this new flag):
https://gitlab.freedesktop.org/mesa/drm/-/merge_requests/286
Alex Deucher (6):
drm/amdgpu: add UAPI for allocating doorbell memory
drm/amdgpu: replace aper_base_kaddr with vram_aper_base_kaddr
drm/amdgpu: rename gmc.aper_base/size
drm/amdgpu: rename doorbell variables
drm/amdgpu: accommodate DOMAIN/PL_DOORBELL
drm/amdgpu: get doorbell memory
Shashank Sharma (2):
drm/amdgpu: create doorbell kernel object
drm/amdgpu: start using kernel doorbell bo
drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c | 13 ++--
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 67 +++++++++-----------
drivers/gpu/drm/amd/amdgpu/amdgpu_doorbell.h | 6 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_fdinfo.c | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_gmc.h | 4 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_mes.c | 2 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 32 +++++++---
drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 3 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 51 ++++++++++++---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.h | 11 +++-
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 15 +++--
drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 3 +-
drivers/gpu/drm/amd/amdgpu/amdgpu_vram_mgr.c | 2 +-
drivers/gpu/drm/amd/amdgpu/gfx_v9_0.c | 2 +-
drivers/gpu/drm/amd/amdgpu/gmc_v10_0.c | 10 +--
drivers/gpu/drm/amd/amdgpu/gmc_v11_0.c | 10 +--
drivers/gpu/drm/amd/amdgpu/gmc_v6_0.c | 6 +-
drivers/gpu/drm/amd/amdgpu/gmc_v7_0.c | 12 ++--
drivers/gpu/drm/amd/amdgpu/gmc_v8_0.c | 10 +--
drivers/gpu/drm/amd/amdgpu/gmc_v9_0.c | 10 +--
drivers/gpu/drm/amd/amdgpu/nbio_v2_3.c | 4 +-
drivers/gpu/drm/amd/amdgpu/nbio_v4_3.c | 4 +-
drivers/gpu/drm/amd/amdgpu/nbio_v6_1.c | 4 +-
drivers/gpu/drm/amd/amdgpu/nbio_v7_2.c | 4 +-
drivers/gpu/drm/amd/amdgpu/nbio_v7_4.c | 4 +-
drivers/gpu/drm/amd/amdgpu/nbio_v7_7.c | 4 +-
drivers/gpu/drm/amd/amdgpu/psp_v11_0.c | 10 +--
drivers/gpu/drm/amd/amdgpu/psp_v13_0.c | 10 +--
drivers/gpu/drm/amd/amdkfd/kfd_migrate.c | 4 +-
include/uapi/drm/amdgpu_drm.h | 7 +-
31 files changed, 193 insertions(+), 137 deletions(-)
--
2.34.1
next reply other threads:[~2023-02-14 16:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 16:15 Shashank Sharma [this message]
2023-02-14 16:15 ` [PATCH v2 1/8] drm/amdgpu: add UAPI for allocating doorbell memory Shashank Sharma
2023-02-14 18:22 ` Christian König
2023-02-14 19:02 ` Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 2/8] drm/amdgpu: replace aper_base_kaddr with vram_aper_base_kaddr Shashank Sharma
2023-02-14 18:24 ` Christian König
2023-02-14 19:03 ` Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 3/8] drm/amdgpu: rename gmc.aper_base/size Shashank Sharma
2023-02-14 18:25 ` Christian König
2023-02-14 16:15 ` [PATCH v2 4/8] drm/amdgpu: rename doorbell variables Shashank Sharma
2023-02-14 18:27 ` Christian König
2023-02-14 19:16 ` Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 5/8] drm/amdgpu: accommodate DOMAIN/PL_DOORBELL Shashank Sharma
2023-02-14 18:31 ` Christian König
2023-02-14 19:24 ` Shashank Sharma
2023-02-15 6:17 ` Christian König
2023-02-15 13:32 ` Shashank Sharma
2023-02-15 13:36 ` Christian König
2023-02-15 13:45 ` Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 6/8] drm/amdgpu: get doorbell memory Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 7/8] drm/amdgpu: create doorbell kernel object Shashank Sharma
2023-02-14 18:35 ` Christian König
2023-02-14 19:26 ` Shashank Sharma
2023-02-16 13:13 ` Shashank Sharma
2023-02-14 16:15 ` [PATCH v2 8/8] drm/amdgpu: start using kernel doorbell bo Shashank Sharma
2023-02-14 18:40 ` Christian König
2023-02-14 19:28 ` Shashank Sharma
2023-02-15 6:18 ` Christian König
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=20230214161510.2153-1-shashank.sharma@amd.com \
--to=shashank.sharma@amd.com \
--cc=Arvind.Yadav@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=contactshashanksharma@gmail.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