From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
Dave Airlie <airlied@redhat.com>,
Daniel Vetter <daniel.vetter@ffwll.ch>
Subject: [Intel-xe] [PATCH 0/1] drm: Add a gpu page-table walker
Date: Thu, 16 Feb 2023 17:27:28 +0100 [thread overview]
Message-ID: <20230216162729.219979-1-thomas.hellstrom@linux.intel.com> (raw)
A slightly unusual cover letter for a single patch.
The page table walker is currently used by the xe driver only,
but the code is generic so we can be good citizens and add it to drm
as a helper, for possible use by other drivers,
If so we can merge the commit when we merge the xe driver.
The question raised here is
*) Should it be a generic drm helper or xe-specific with changed
prefixes?
*) If a drm helper, should we use a config option?
For usage examples, see xe_pt.c
https://gitlab.freedesktop.org/drm/xe/kernel/-/blob/drm-xe-next/drivers/gpu/drm/xe/xe_pt.c
Thanks,
Thomas
Thomas Hellström (1):
drm: Add a gpu page-table walker helper
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/drm_pt_walk.c | 159 +++++++++++++++++++++++++++++++++
include/drm/drm_pt_walk.h | 161 ++++++++++++++++++++++++++++++++++
3 files changed, 321 insertions(+)
create mode 100644 drivers/gpu/drm/drm_pt_walk.c
create mode 100644 include/drm/drm_pt_walk.h
--
2.34.1
next reply other threads:[~2023-02-16 16:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 16:27 Thomas Hellström [this message]
2023-02-16 16:27 ` [Intel-xe] [PATCH 1/1] drm: Add a gpu page-table walker helper Thomas Hellström
2023-02-16 20:18 ` [Intel-xe] [PATCH 0/1] drm: Add a gpu page-table walker Daniel Vetter
2023-02-23 14:38 ` Thomas Hellström
2023-02-23 18:50 ` Alex Deucher
2023-02-26 18:56 ` Oded Gabbay
2023-02-27 8:09 ` Thomas Hellström
2023-02-27 15:07 ` Stanislaw Gruszka
2023-02-27 8:07 ` Thomas Hellström
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=20230216162729.219979-1-thomas.hellstrom@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=airlied@redhat.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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