public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Claude Code Review Bot <claude-review@example.com>
To: dri-devel-reviews@example.com
Subject: Claude review: Support sparse mappings in Panthor
Date: Thu, 23 Apr 2026 07:41:44 +1000	[thread overview]
Message-ID: <review-overall-20260422122538.3117380-1-adrian.larumbe@collabora.com> (raw)
In-Reply-To: <20260422122538.3117380-1-adrian.larumbe@collabora.com>

Overall Series Review

Subject: Support sparse mappings in Panthor
Author: =?UTF-8?q?Adri=C3=A1n=20Larumbe?= <adrian.larumbe@collabora.com>
Patches: 7
Reviewed: 2026-04-23T07:41:44.304387

---

This v9 series adds sparse mapping support to the Panthor (Mali CSF) GPU driver, allowing userspace (Vulkan) to bind virtual address ranges over a kernel-allocated dummy BO in a cyclic fashion. The approach of per-file-context dummy BOs for information isolation is sound, and the series is well-structured with clean preparatory patches.

However, there are several issues that need attention:

1. **uAPI enum ordering break** (Patch 1) — inserting `DRM_PANTHOR_DEV_QUERY_MMU_INFO` in the middle of an auto-numbered enum changes the values of all subsequent members, breaking existing userspace.
2. **Memory leak on error path** (Patch 5) — `panthor_vm_pool_create` leaks memory if `panthor_dummy_bo_create` fails.
3. **Wrong address in hugepage alignment check** (Patch 5) — the `op->next` branch of `unmap_hugepage_align` now passes `*unmap_start` instead of the original `unmap_end - 1`, which is incorrect for non-sparse mappings.

---

---
Generated by Claude Code Patch Reviewer

  parent reply	other threads:[~2026-04-22 21:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-22 12:25 [PATCH v9 0/6] Support sparse mappings in Panthor Adrián Larumbe
2026-04-22 12:25 ` [PATCH v9 1/6] drm/panthor: Expose GPU page sizes to UM Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 12:25 ` [PATCH v9 2/6] drm/panthor: Pass vm_bind_op to vm_prepare_map_op_ctx Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 12:25 ` [PATCH v9 3/6] drm/panthor: Delete spurious whitespace from uAPI header Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 12:25 ` [PATCH v9 4/6] drm/panthor: Remove unused operation context field Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 12:25 ` [PATCH v9 5/6] drm/panthor: Support sparse mappings Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 12:25 ` [PATCH v9 6/6] drm/panthor: Bump the driver version to 1.9 Adrián Larumbe
2026-04-22 21:41   ` Claude review: " Claude Code Review Bot
2026-04-22 21:41 ` Claude Code Review Bot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2026-04-29 18:32 [PATCH v10 0/6] Support sparse mappings in Panthor Adrián Larumbe
2026-05-05  1:14 ` Claude review: " 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=review-overall-20260422122538.3117380-1-adrian.larumbe@collabora.com \
    --to=claude-review@example.com \
    --cc=dri-devel-reviews@example.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