From: Sanjay Yadav <sanjay.kumar.yadav@intel.com>
To: dri-devel@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org,
Christian König <christian.koenig@amd.com>,
Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>,
Matthew Auld <matthew.auld@intel.com>
Subject: [PATCH v2 0/2] drm/buddy: Documentation and internal helper cleanup
Date: Wed, 11 Feb 2026 11:01:24 +0530 [thread overview]
Message-ID: <20260211053123.260037-4-sanjay.kumar.yadav@intel.com> (raw)
This series improves the GPU buddy allocator by adding missing
documentation and cleaning up internal helpers.
It adds kernel-doc for the allocator structures and flags, covering
gpu_buddy, gpu_buddy_block, and the allocation flags (RANGE, TOPDOWN,
CONTIGUOUS, CLEAR, TRIM_DISABLE) to make the allocator’s design and usage
clearer for readers and contributors.
It also reduces the header surface by moving internal helpers from
gpu_buddy.h into buddy.c as static functions, since they have no
external users, and removes gpu_get_buddy(), an unused exported wrapper
around the internal __get_buddy() helper. This clarifies the intended API
and avoids exporting unused symbols.
No functional changes.
v2:
- Rebased after DRM buddy allocator moved to drivers/gpu/
- Keep gpu_buddy_block_is_free() in header since it's now
used by drm_buddy.c
- Corrected GPU_BUDDY_CLEAR_TREE and GPU_BUDDY_DIRTY_TREE index values (Arun)
- Updated commit message and cover letter to reflect changes
Cc: Christian König <christian.koenig@amd.com>
Cc: Arunpravin Paneer Selvam <Arunpravin.PaneerSelvam@amd.com>
Suggested-by: Matthew Auld <matthew.auld@intel.com>
Sanjay Yadav (2):
drm/buddy: Add kernel-doc for allocator structures and flags
drm/buddy: Move internal helpers to buddy.c
drivers/gpu/buddy.c | 35 ++++-----
include/linux/gpu_buddy.h | 147 +++++++++++++++++++++++++++-----------
2 files changed, 122 insertions(+), 60 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-11 5:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 5:31 Sanjay Yadav [this message]
2026-02-11 5:31 ` [PATCH v2 1/2] drm/buddy: Add kernel-doc for allocator structures and flags Sanjay Yadav
2026-02-11 6:07 ` Claude review: " Claude Code Review Bot
2026-02-12 7:38 ` [PATCH v2 1/2] " Arunpravin Paneer Selvam
2026-02-12 7:40 ` Arunpravin Paneer Selvam
2026-02-12 9:23 ` Yadav, Sanjay Kumar
2026-02-11 5:31 ` [PATCH v2 2/2] drm/buddy: Move internal helpers to buddy.c Sanjay Yadav
2026-02-11 6:07 ` Claude review: " Claude Code Review Bot
2026-02-11 6:07 ` Claude review: drm/buddy: Documentation and internal helper cleanup Claude Code Review Bot
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=20260211053123.260037-4-sanjay.kumar.yadav@intel.com \
--to=sanjay.kumar.yadav@intel.com \
--cc=Arunpravin.PaneerSelvam@amd.com \
--cc=christian.koenig@amd.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.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