From: Zack Rusin <zack@kde.org>
To: dri-devel@lists.freedesktop.org
Cc: David Airlie <airlied@linux.ie>,
krastevm@vmware.com, Huang Rui <ray.huang@amd.com>,
Christian Koenig <christian.koenig@amd.com>,
mombasawalam@vmware.com
Subject: [PATCH v2 0/5] drm/ttm: Introduce TTM res manager debugfs helpers
Date: Mon, 11 Apr 2022 23:35:21 -0400 [thread overview]
Message-ID: <20220412033526.369115-1-zack@kde.org> (raw)
From: Zack Rusin <zackr@vmware.com>
v2: Switch to using ttm_resource_manager's directly in the debugfs
callbacks
This series introduces generic TTM resource manager debugfs helpers and
refactors TTM drivers which have been using hand rolled out versions
of those to use the new code.
Zack Rusin (5):
drm/ttm: Add common debugfs code for resource managers
drm/vmwgfx: Add debugfs entries for various ttm resource managers
drm/amdgpu: Use TTM builtin resource manager debugfs code
drm/qxl: Use TTM builtin resource manager debugfs code
drm/radeon: Use TTM builtin resource manager debugfs code
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 86 +++++--------------------
drivers/gpu/drm/qxl/qxl_ttm.c | 39 ++---------
drivers/gpu/drm/radeon/radeon_ttm.c | 36 ++---------
drivers/gpu/drm/ttm/ttm_resource.c | 34 ++++++++++
drivers/gpu/drm/vmwgfx/vmwgfx_drv.c | 18 ++++++
include/drm/ttm/ttm_resource.h | 4 ++
6 files changed, 84 insertions(+), 133 deletions(-)
--
2.32.0
next reply other threads:[~2022-04-12 3:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 3:35 Zack Rusin [this message]
2022-04-12 3:35 ` [PATCH v2 1/5] drm/ttm: Add common debugfs code for resource managers Zack Rusin
2022-04-12 3:35 ` [PATCH v2 2/5] drm/vmwgfx: Add debugfs entries for various ttm " Zack Rusin
2022-04-12 3:35 ` [PATCH v2 3/5] drm/amdgpu: Use TTM builtin resource manager debugfs code Zack Rusin
2022-04-12 3:35 ` [PATCH v2 4/5] drm/qxl: " Zack Rusin
2022-04-12 3:35 ` [PATCH v2 5/5] drm/radeon: " Zack Rusin
2022-04-12 9:15 ` [PATCH v2 0/5] drm/ttm: Introduce TTM res manager debugfs helpers Christian König
2022-04-18 20:09 ` Zack Rusin
2022-04-19 6:16 ` 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=20220412033526.369115-1-zack@kde.org \
--to=zack@kde.org \
--cc=airlied@linux.ie \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=krastevm@vmware.com \
--cc=mombasawalam@vmware.com \
--cc=ray.huang@amd.com \
--cc=zackr@vmware.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;
as well as URLs for NNTP newsgroup(s).