intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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
Date: Mon, 04 May 2026 15:43:14 -0000	[thread overview]
Message-ID: <177790939425.35772.8135583948756758799@5ab824fced77> (raw)
In-Reply-To: <20260504135343.1797869-1-francois.dugast@intel.com>

== Series Details ==

Series: gpu/buddy: Per-order free and used block scoreboards
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
c8c12e558adaef7a4d125d83b6e1f8824bc13b82
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 9f4f941cfd0d7c0a98dd0713cff5d28597dc1440
Author: Francois Dugast <francois.dugast@intel.com>
Date:   Mon May 4 15:52:42 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().
    
    Signed-off-by: Francois Dugast <francois.dugast@intel.com>
    Assisted-by: GitHub Copilot:claude-sonnet-4.6
+ /mt/dim checkpatch e798c5cca30e83c5793aa3d6f22456e39eeb219c drm-intel
57294be1773b gpu/buddy: Track per-order free 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, 132 lines checked
9f4f941cfd0d gpu/buddy: Track per-order used blocks with a scoreboard
-:16: WARNING:BAD_SIGN_OFF: Assisted-by expects 'AGENT_NAME:MODEL_VERSION [TOOL1] [TOOL2]' format
#16: 
Assisted-by: GitHub Copilot:claude-sonnet-4.6

total: 0 errors, 1 warnings, 0 checks, 108 lines checked



  parent reply	other threads:[~2026-05-04 15:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-04 13:52 [PATCH 0/2] gpu/buddy: Per-order free and used block scoreboards Francois Dugast
2026-05-04 13:52 ` [PATCH 1/2] gpu/buddy: Track per-order free blocks with a scoreboard Francois Dugast
2026-05-08 14:09   ` Matthew Auld
2026-05-04 13:52 ` [PATCH 2/2] gpu/buddy: Track per-order used " Francois Dugast
2026-05-08 14:13   ` Matthew Auld
2026-05-12  7:04     ` Francois Dugast
2026-05-04 15:43 ` Patchwork [this message]
2026-05-04 15:44 ` ✓ CI.KUnit: success for gpu/buddy: Per-order free and used block scoreboards Patchwork
2026-05-04 17:05 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-04 20:44 ` ✓ Xe.CI.FULL: " 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=177790939425.35772.8135583948756758799@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).