From: Xin Wang <x.wang@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Xin Wang <x.wang@intel.com>
Subject: [PATCH] drm/xe: restric multi-lrc to VCS/VECS engines
Date: Wed, 18 Feb 2026 05:50:33 +0000 [thread overview]
Message-ID: <20260218055033.327926-1-x.wang@intel.com> (raw)
Remove multi-lrc support on non‑media engines for ModSched
platforms, since GuC firmware no longer supports this and
there’s no valid use case.
Signed-off-by: Xin Wang <x.wang@intel.com>
---
drivers/gpu/drm/xe/xe_exec_queue.c | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/drivers/gpu/drm/xe/xe_exec_queue.c b/drivers/gpu/drm/xe/xe_exec_queue.c
index 66d0e10ee2c4..9f5e9d78c8c6 100644
--- a/drivers/gpu/drm/xe/xe_exec_queue.c
+++ b/drivers/gpu/drm/xe/xe_exec_queue.c
@@ -1200,6 +1200,15 @@ int xe_exec_queue_create_ioctl(struct drm_device *dev, void *data,
return -ENOENT;
}
+ /* multi-lrc is only supported on VIDEO_DECODE and VIDEO_ENHANCE engines */
+ if (XE_IOCTL_DBG(xe, args->width > 1 && GRAPHICS_VER(xe) > 20 &&
+ !(eci[0].engine_class == DRM_XE_ENGINE_CLASS_VIDEO_DECODE ||
+ eci[0].engine_class == DRM_XE_ENGINE_CLASS_VIDEO_ENHANCE))) {
+ up_read(&vm->lock);
+ xe_vm_put(vm);
+ return -EOPNOTSUPP;
+ }
+
/* SRIOV sched groups are not compatible with multi-lrc */
if (XE_IOCTL_DBG(xe, args->width > 1 && has_sched_groups(hwe->gt))) {
up_read(&vm->lock);
--
2.43.0
next reply other threads:[~2026-02-18 5:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 5:50 Xin Wang [this message]
2026-02-18 5:57 ` ✓ CI.KUnit: success for drm/xe: restric multi-lrc to VCS/VECS engines Patchwork
2026-02-18 6:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 6:44 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-18 13:57 ` ✓ CI.KUnit: success for drm/xe: restric multi-lrc to VCS/VECS engines (rev2) Patchwork
2026-02-18 14:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-18 16:07 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-18 22:39 ` [PATCH] drm/xe: restric multi-lrc to VCS/VECS engines Lin, Shuicheng
2026-02-18 22:54 ` Matt Roper
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=20260218055033.327926-1-x.wang@intel.com \
--to=x.wang@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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