From: Matthew Auld <matthew.auld@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [PATCH] drm/xe: Don't fall through on DRM_GPUVA_OP_DRIVER in op_check_svm_userptr
Date: Fri, 10 Jul 2026 16:14:34 +0100 [thread overview]
Message-ID: <74396ae4-3503-466a-8c3e-02bc56a55628@intel.com> (raw)
In-Reply-To: <20260710141259.1512070-1-mika.kuoppala@linux.intel.com>
Hi,
On 10/07/2026 15:12, Mika Kuoppala wrote:
> The DRM_GPUVA_OP_DRIVER operation is used by eudebug (and potentially
> other driver ops). Because the break was inside the #if GPUSVM block,
> we fell through and printed the "NOT POSSIBLE" warning.
I think throwing a warn with "NOT POSSIBLE" was maybe not the wrong
thing wrt SVM and the current driver code, in the sense that there would
be a bug somewhere if we reach here without GPUSVM support?
Are you triggering this only with upcoming eudebug? i.e there is a new
DRM_GPUVA_OP_DRIVER user, which is not SVM?
>
> Fixes: 7477c4bd20dc ("drm/xe/pt: unify xe_pt_svm_pre_commit with userptr")
I think maybe drop the fixes, and tweak the commit to make it clear that
this is just prep work for a new user?
> Cc: Matthew Auld <matthew.auld@intel.com>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
> ---
> drivers/gpu/drm/xe/xe_pt.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pt.c b/drivers/gpu/drm/xe/xe_pt.c
> index 7111b5d0f6aa..f5ce1fcf484c 100644
> --- a/drivers/gpu/drm/xe/xe_pt.c
> +++ b/drivers/gpu/drm/xe/xe_pt.c
> @@ -1547,8 +1547,8 @@ static int op_check_svm_userptr(struct xe_vm *vm, struct xe_vma_op *op,
> err = vma_check_userptr(vm, gpuva_to_vma(op->base.prefetch.va), pt_update);
> }
> break;
> -#if IS_ENABLED(CONFIG_DRM_XE_GPUSVM)
> case DRM_GPUVA_OP_DRIVER:
> +#if IS_ENABLED(CONFIG_DRM_XE_GPUSVM)
> if (op->subop == XE_VMA_SUBOP_MAP_RANGE) {
> struct xe_svm_range *range = op->map_range.range;
>
> @@ -1561,8 +1561,8 @@ static int op_check_svm_userptr(struct xe_vm *vm, struct xe_vma_op *op,
> return -EAGAIN;
> }
> }
> - break;
> #endif
> + break;
> default:
> drm_warn(&vm->xe->drm, "NOT POSSIBLE");
> }
next prev parent reply other threads:[~2026-07-10 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-10 14:12 [PATCH] drm/xe: Don't fall through on DRM_GPUVA_OP_DRIVER in op_check_svm_userptr Mika Kuoppala
2026-07-10 14:20 ` ✓ CI.KUnit: success for " Patchwork
2026-07-10 15:14 ` Matthew Auld [this message]
2026-07-10 15:28 ` [PATCH] " Matthew Auld
2026-07-13 13:19 ` Mika Kuoppala
2026-07-10 15:32 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-07-11 1:07 ` ✓ 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=74396ae4-3503-466a-8c3e-02bc56a55628@intel.com \
--to=matthew.auld@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.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