Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Himal Prasad Ghimiray" <himal.prasad.ghimiray@intel.com>
Cc: dri-devel@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Subject: Re: [RFC 2/7] drm/ttm: Add NUMA node aware restore helpers
Date: Mon, 02 Nov 2026 10:26:24 +0000	[thread overview]
Message-ID: <sashiko-outbox-193253@kernel.org> (raw)
In-Reply-To: <20261102101803.455921-11-himal.prasad.ghimiray@intel.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] drm/ttm: unused helper and EXPORT_SYMBOL() on ttm_pool_restore_and_alloc()
--

commit 8d0a6d62696c67cc37673b025155aa37dad8e6a7
Author: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>

drm/ttm: Add NUMA node aware restore helpers

This commit introduces ttm_tt_restore_node() and
ttm_pool_restore_and_alloc_node() so callers can preserve a specific NUMA
node placement when restoring backed-up TTM pages.

> diff --git a/drivers/gpu/drm/ttm/ttm_pool.c b/drivers/gpu/drm/ttm/ttm_pool.c
> index 54d2f6b5c229c..2107dc6c69b36 100644
> --- a/drivers/gpu/drm/ttm/ttm_pool.c
> +++ b/drivers/gpu/drm/ttm/ttm_pool.c
> @@ -962,6 +962,30 @@ EXPORT_SYMBOL(ttm_pool_alloc_node);
>   */
>  int ttm_pool_restore_and_alloc(struct ttm_pool *pool, struct ttm_tt *tt,
>  			       const struct ttm_operation_ctx *ctx)
> +{
> +	return ttm_pool_restore_and_alloc_node(pool, tt, ctx, NUMA_NO_NODE);
> +}
> +EXPORT_SYMBOL(ttm_pool_restore_and_alloc);

[Severity: Low]
Is ttm_pool_restore_and_alloc() still needed now that ttm_tt_restore() in
drivers/gpu/drm/ttm/ttm_tt.c delegates to ttm_tt_restore_node(), which
calls ttm_pool_restore_and_alloc_node() directly?

Previously, ttm_pool_restore_and_alloc() was an unexported TTM-internal
helper whose only caller was ttm_tt_restore(), and external drivers cannot
call it directly because only ttm_tt_restore() and ttm_tt_restore_node()
clear TTM_TT_FLAG_BACKED_UP on tt->page_flags. With ttm_tt_restore()
switched over to ttm_tt_restore_node(), ttm_pool_restore_and_alloc() has no
remaining callers in the tree, yet it is kept and newly exported with
EXPORT_SYMBOL().

Should ttm_pool_restore_and_alloc() and its EXPORT_SYMBOL() be dropped (or
kept unexported if there is a planned internal user)?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261102101803.455921-9-himal.prasad.ghimiray@intel.com?part=2

  reply	other threads:[~2026-11-02 10:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-02 10:18 [RFC 0/7] drm/ttm, drm/xe: Per-BO host NUMA node placement Himal Prasad Ghimiray
2026-11-02 10:18 ` [RFC 1/7] drm/ttm/pool: Add ttm_pool_alloc_node() for caller-selected NUMA node Himal Prasad Ghimiray
2026-11-02 10:26   ` sashiko-bot
2026-11-02 10:50   ` Christian König
2026-11-02 12:46     ` Thomas Hellström
2026-11-02 10:18 ` [RFC 2/7] drm/ttm: Add NUMA node aware restore helpers Himal Prasad Ghimiray
2026-11-02 10:26   ` sashiko-bot [this message]
2026-11-02 10:18 ` [RFC 3/7] drm/ttm/pool: enforce per-node cache limits on free Himal Prasad Ghimiray
2026-11-02 10:18 ` [RFC 4/7] drm/xe/bo: Plumb a per-BO host NUMA node hint into tt populate Himal Prasad Ghimiray
2026-11-02 10:18 ` [RFC 5/7] drm/xe/bo: Preserve the host NUMA node across backup / restore Himal Prasad Ghimiray
2026-11-02 10:18 ` [RFC 6/7] drm/xe/uapi: Add GEM_CREATE NUMA node placement property Himal Prasad Ghimiray
2026-11-02 10:27   ` sashiko-bot
2026-11-02 10:18 ` [RFC 7/7] drm/xe/uapi: Wire up GEM_CREATE NUMA node placement handler Himal Prasad Ghimiray
2026-11-02 10:29   ` sashiko-bot
2026-11-02 11:12   ` Matthew Auld
2026-11-02 18:24     ` Himal prasad Ghimiray
2026-11-02 12:44 ` ✓ CI.KUnit: success for drm/ttm, drm/xe: Per-BO host NUMA node placement Patchwork
2026-11-02 13:22 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-02 14:55 ` ✓ 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=sashiko-outbox-193253@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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