From: sashiko-bot@kernel.org
To: "Matthew Brost" <matthew.brost@intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v3 2/2] drm/xe: Add debugfs stats for DMA-mapped pages per order
Date: Fri, 13 Nov 2026 19:39:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-213558@kernel.org> (raw)
In-Reply-To: <20261113190128.2118723-2-matthew.brost@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] drm/xe: build failure in xe_userptr.c when
CONFIG_DRM_XE_GPUSVM=n
--
commit cdf22e3bf1d70b7d0f7e88b6b7825cfa6ceeb290
Author: Thomas Hellström <thomas.hellstrom@linux.intel.com>
drm/xe: Add debugfs stats for DMA-mapped pages per order
This commit adds per-order DMA-mapped system page counters for TTM buffer
objects and GPU SVM / userptr ranges, and exposes them in debugfs at
dma_mapped_pages.
> diff --git a/drivers/gpu/drm/xe/xe_userptr.c b/drivers/gpu/drm/xe/xe_userptr.c
> index 9c1dac0fce6f1..e657d7886a96b 100644
> --- a/drivers/gpu/drm/xe/xe_userptr.c
> +++ b/drivers/gpu/drm/xe/xe_userptr.c
> @@ -8,9 +8,38 @@
>
> #include <linux/mm.h>
>
> +#include <drm/drm_pagemap.h>
> +
> +#include "xe_svm.h"
> #include "xe_tlb_inval.h"
> #include "xe_trace_bo.h"
>
> +#if IS_ENABLED(CONFIG_DEBUG_FS)
> +static const struct drm_gpusvm_ops xe_userptr_gpusvm_ops = {
> + .dma_map_account = xe_svm_dma_map_account,
> +};
> +#endif
[Severity: High]
Does xe_userptr.c fail to build when CONFIG_DRM_XE_GPUSVM=n,
CONFIG_DRM_GPUSVM=y and CONFIG_DEBUG_FS=y?
xe_userptr.o is built under CONFIG_DRM_GPUSVM, whereas
xe_svm_dma_map_account() is declared in the #if
IS_ENABLED(CONFIG_DRM_XE_GPUSVM) block of xe_svm.h and defined in xe_svm.c
(which is only built under CONFIG_DRM_XE_GPUSVM). Moving
xe_svm_dma_map_account() to a header or into xe_userptr.c so both
configurations can use it would avoid the undeclared identifier error.
Also, xe_userptr.c already includes "xe_svm.h" at the top of the file, so
the new #include "xe_svm.h" is a duplicate.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261113190128.2118723-1-matthew.brost@intel.com?part=2
next prev parent reply other threads:[~2026-11-13 19:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 19:01 [PATCH v3 1/2] drm/gpusvm: Add a DMA-mapping accounting callback Matthew Brost
2026-11-13 19:01 ` [PATCH v3 2/2] drm/xe: Add debugfs stats for DMA-mapped pages per order Matthew Brost
2026-11-13 19:39 ` sashiko-bot [this message]
2026-11-13 19:08 ` ✗ CI.checkpatch: warning for series starting with [v3,1/2] drm/gpusvm: Add a DMA-mapping accounting callback Patchwork
2026-11-13 19:10 ` ✓ CI.KUnit: success " Patchwork
2026-11-13 19:19 ` [PATCH v3 1/2] " sashiko-bot
2026-11-13 19:43 ` ✗ Xe.CI.BAT: failure for series starting with [v3,1/2] " 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-213558@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox