From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Francois Dugast" <francois.dugast@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✗ CI.checkpatch: warning for gpu/buddy: Per-order free and used block scoreboards (rev3)
Date: Tue, 12 May 2026 12:33:30 -0000 [thread overview]
Message-ID: <177858921053.61707.1253629425710817490@5ab824fced77> (raw)
In-Reply-To: <20260511164217.150237-1-francois.dugast@intel.com>
== Series Details ==
Series: gpu/buddy: Per-order free and used block scoreboards (rev3)
URL : https://patchwork.freedesktop.org/series/165914/
State : warning
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
061140b9bc586ae7f40abc1249c97e1cc72d1b9d
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 1644f68e601283ea1dfcd47029099f2dcd89e3ae
Author: Francois Dugast <francois.dugast@intel.com>
Date: Mon May 11 18:41:06 2026 +0200
gpu/buddy: Track per-order used blocks with a scoreboard
Extend the scoreboard approach from the previous commit to used blocks,
so drm_buddy_print() can report per-order allocation pressure in O(1).
Unlike free blocks, an allocated block can leave the allocated state
through mark_free() (normal free and gpu_buddy_block_trim()) or be
consumed directly by gpu_block_free() during coalescing. Both sites are
guarded by gpu_buddy_block_is_allocated() and paired with the increment
in mark_allocated().
v2:
- Update after fix for use-after-free in split_block() call sites
- Change goto label to out_free_used_scoreboard for clarity
- Make drm_buddy_print() and gpu_buddy_print() symmetric for used and
free
Signed-off-by: Francois Dugast <francois.dugast@intel.com>
Assisted-by: GitHub Copilot:claude-sonnet-4.6
+ /mt/dim checkpatch b83102e9c06357b09f2cfbe944269786cb6985c4 drm-intel
e1e022f337b4 gpu/buddy: Fix use-after-free in split_block() call sites
-:24: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be immediately followed by Closes: with a URL to the report
#24:
Reported-by: Sashiko <sashiko-bot@kernel.org>
Signed-off-by: Francois Dugast <francois.dugast@intel.com>
-:26: WARNING:BAD_SIGN_OFF: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
#26:
Assisted-by: GitHub Copilot:claude-sonnet-4.6
total: 0 errors, 2 warnings, 0 checks, 44 lines checked
d8c958ca521a gpu/buddy: Track per-order free blocks with a scoreboard
-:25: WARNING:BAD_SIGN_OFF: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
#25:
Assisted-by: GitHub Copilot:claude-sonnet-4.6
total: 0 errors, 1 warnings, 0 checks, 160 lines checked
1644f68e6012 gpu/buddy: Track per-order used blocks with a scoreboard
-:22: WARNING:BAD_SIGN_OFF: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
#22:
Assisted-by: GitHub Copilot:claude-sonnet-4.6
total: 0 errors, 1 warnings, 0 checks, 129 lines checked
next prev parent reply other threads:[~2026-05-12 12:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 16:41 [PATCH v2 0/3] gpu/buddy: Per-order free and used block scoreboards Francois Dugast
2026-05-11 16:41 ` [PATCH v2 1/3] gpu/buddy: Fix use-after-free in split_block() call sites Francois Dugast
2026-05-11 16:41 ` [PATCH v2 2/3] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-15 15:50 ` Matthew Auld
2026-05-11 16:41 ` [PATCH v2 3/3] gpu/buddy: Track per-order used " Francois Dugast
2026-05-11 23:29 ` ✗ CI.checkpatch: warning for gpu/buddy: Per-order free and used block scoreboards (rev2) Patchwork
2026-05-11 23:30 ` ✓ CI.KUnit: success " Patchwork
2026-05-12 1:05 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-05-12 4:13 ` ✗ Xe.CI.FULL: " Patchwork
2026-05-12 12:33 ` Patchwork [this message]
2026-05-12 12:34 ` ✓ CI.KUnit: success for gpu/buddy: Per-order free and used block scoreboards (rev3) Patchwork
2026-05-12 13:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-13 0:43 ` ✗ Xe.CI.FULL: failure " Patchwork
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=177858921053.61707.1253629425710817490@5ab824fced77 \
--to=patchwork@emeril.freedesktop.org \
--cc=francois.dugast@intel.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).