From: sashiko-bot@kernel.org
To: "Matthew Auld" <matthew.auld@intel.com>, intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/xe: Exclude imported dma-buf BOs from the TT budget
Date: Sat, 07 Nov 2026 17:36:57 +0000 [thread overview]
Message-ID: <sashiko-outbox-203113@kernel.org> (raw)
In-Reply-To: <20261107-oom-fun-v1-2-be9eb05b82ed@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [Low] drm/xe: commit message body describes outdated v1
sys_mgr_sg_usage design
--
commit 2d9d97becda400684fed39733d2674585c59c2c5
Author: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
drm/xe: Exclude imported dma-buf BOs from the TT budget
This commit excludes imported dma-buf BOs (ttm_bo_type_sg) from being
charged against the system TTM resource manager budget by tracking
charged allocations in xe->mem.sys_mgr_charged.
> Track the bytes of ttm_bo_type_sg BOs in a new per-device counter,
> mem.sys_mgr_sg_usage, and subtract it from the usage compared against
> the budget. The counter is maintained in xe_ttm_sys_mgr_new() and
> xe_ttm_sys_mgr_del().
[Severity: Low]
This isn't a bug, but this paragraph still describes the v1 design
(tracking ttm_bo_type_sg BOs in mem.sys_mgr_sg_usage and subtracting
them from manager usage), whereas the patch tracks non-imported BOs
directly in mem.sys_mgr_charged.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261107-oom-fun-v1-0-be9eb05b82ed@intel.com?part=2
next prev parent reply other threads:[~2026-11-07 17:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-07 17:26 [PATCH 0/3] Spurious OOM with P2P dma-buf imports on multi-GPU systems Matthew Auld
2026-11-07 17:26 ` [PATCH 1/3] drm/xe: don't allocate fake mmap offsets for imported dma-bufs Matthew Auld
2026-11-07 17:43 ` sashiko-bot
2026-11-07 17:26 ` [PATCH 2/3] drm/xe: Exclude imported dma-buf BOs from the TT budget Matthew Auld
2026-11-07 17:36 ` sashiko-bot [this message]
2026-11-07 17:26 ` [PATCH 3/3] drm/ttm, drm/xe: Drop the ttm_tt on null moves to VRAM Matthew Auld
2026-11-07 17:36 ` ✓ CI.KUnit: success for Spurious OOM with P2P dma-buf imports on multi-GPU systems Patchwork
2026-11-07 18:10 ` ✓ Xe.CI.BAT: " Patchwork
2026-11-08 8:22 ` ✓ 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-203113@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.