From: Matthew Brost <matthew.brost@intel.com>
To: Julia Filipchuk <julia.filipchuk@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Subject: Re: [PATCH v6 2/3] Reapply "drm/xe/xe2: Enable Indirect Ring State support for Xe2"
Date: Tue, 24 Feb 2026 10:07:28 -0800 [thread overview]
Message-ID: <aZ3o4KbEvRgATkaP@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <3114cb01-228a-4016-8e45-146202aa7828@intel.com>
On Tue, Feb 24, 2026 at 09:51:46AM -0800, Julia Filipchuk wrote:
> On 2/20/2026 9:11 AM, Matthew Brost wrote:
> > On Fri, Feb 20, 2026 at 09:01:38AM -0800, Julia Filipchuk wrote:
> >> This reverts commit 03d85ab36bcbcbe9dc962fccd3f8e54d7bb93b35.
> >>
> >> Previously this was reverted due to failures on LRC context switch.
> >> Issues should be root-caused and resolved with GuC WA 14025515070. Now
> >> setting indirect ring state is available by default.
> >>
> >> Note: Will be cleared if WA not available due to older GuC version.
> >>
> >
> > Is there a reason we need indirect ring state on Xe2? AFAIK, this is
> > only needed for multi-Q or if we did user-space submission. I’d rather
> > not have an officially supported kernel floating around on Xe2 with a
> > mis-match of indirect direct ring state enabled, since it’s a very
> > subtle delta that could surface in odd ways.
> >
> > IMO, it’s best to leave indirect ring state off on Xe2 unless we have a
> > concrete reason to enable it.
> >
> > Matt
>
> Thank you for input. Changing to leave off for Xe2 for now.
I think we should merge the WA though so if we want to experiment on Xe2
for features which require indirect ring state (UMD submission) we don't
trip up on the indirect ring state Xe2 bug.
Matt
next prev parent reply other threads:[~2026-02-24 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 17:01 [PATCH v6 0/3] drm/xe: Enable Wa_14025515070, Enable indirect ring state for XE2+ Julia Filipchuk
2026-02-20 17:01 ` [PATCH v6 1/3] drm/xe: Enable Wa_14025515070 Julia Filipchuk
2026-02-23 23:53 ` Daniele Ceraolo Spurio
2026-02-20 17:01 ` [PATCH v6 2/3] Reapply "drm/xe/xe2: Enable Indirect Ring State support for Xe2" Julia Filipchuk
2026-02-20 17:11 ` Matthew Brost
2026-02-24 17:51 ` Julia Filipchuk
2026-02-24 18:07 ` Matthew Brost [this message]
2026-02-20 17:01 ` [PATCH v6 3/3] Revert "drm/xe/xe3p_xpc: Enable Indirect Ring State for xe3p_xpc" Julia Filipchuk
2026-02-20 17:07 ` ✗ CI.checkpatch: warning for drm/xe: Enable Wa_14025515070, Enable indirect ring state for XE2+ (rev6) Patchwork
2026-02-20 17:09 ` ✓ CI.KUnit: success " Patchwork
2026-02-20 18:15 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-21 7:54 ` ✗ Xe.CI.FULL: failure " 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=aZ3o4KbEvRgATkaP@lstrano-desk.jf.intel.com \
--to=matthew.brost@intel.com \
--cc=daniele.ceraolospurio@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=julia.filipchuk@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