From: Daniel Charles <daniel.charles@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, <intel-xe@lists.freedesktop.org>
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Ashutosh Dixit <ashutosh.dixit@intel.com>
Subject: Re: [PATCH v3 0/4] Add debugfs facility to catch RTP mistakes
Date: Mon, 23 Feb 2026 09:40:31 -0800 [thread overview]
Message-ID: <02b09764-52db-4b81-aa31-37e588953a0e@intel.com> (raw)
In-Reply-To: <20260213000929.732113-6-matthew.d.roper@intel.com>
On 2/12/2026 4:09 PM, Matt Roper wrote:
> Unlike i915, Xe doesn't currently do any readback verification of
> workaround/tuning settings that it tries to program. If an entry gets
> placed on the wrong table, or applied to the wrong platform/IP, the
> programming may be silently ineffective without anyone noticing.
>
> i915's solution of doing verification at application time was
> problematic because raising warnings during probe would be treated by CI
> as a fatal problem and would prevent CI from even attempting any other
> testing until the issue was dealt with. Let's avoid that with Xe and
> instead perform the verification on-demand when a debugfs entry is read.
> This makes it very easy to do verification at various times during
> manual debugging. It should also be simply to wrap a dedicated IGT test
> around the debugfs entry such that any unexpected failures are reported
> against that one test rather than bringing down the entire CI system.
>
> Note that verification of LRC programming is a bit more complicated than
> verification of GT/engine programming since we can't just blindly read
> the register values from the CPU and expect the RTP values to be in
> effect. Applying LRC progamming ensures that every GPU context created
> should have the updated values in the LRC, and those values will get
> loaded into the register when the hardware context switches to it.
> However when no context is running on the hardware, the register values
> may revert to their hardware defaults which do not have the programming
> applied. Instead, we should verify LRC programming by parsing the
> engine's 'default LRC' image and making sure the desired programming
> appears somewhere in one of the MI_LOAD_REGISTER_IMM state emission
> commands.
>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
> Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
>
> v2:
> - Avoid processing RTP -> SR for gt/hwe lists in VF to ensure the
> debugfs entry is safe to use in an SR-IOV VF. (Ashutosh)
> - Add verification of LRC adjustments by searching engine type's
> default LRC.
>
> v3:
> - Add missing checks to avoid SR-IOV VF processing of RTP -> SR in
> hw_engine_setup_default_state() and
> xe_reg_whitelist_process_engine().
>
> Matt Roper (4):
> drm/xe/reg_sr: Don't process gt/hwe lists in VF
> drm/xe/reg_sr: Add debugfs to verify status of reg_sr programming
> drm/xe: Add facility to lookup the value of a register in a default
> LRC
> drm/xe/reg_sr: Allow register_save_restore_check debugfs to verify LRC
> values
I reviewed the series and I have no further comments.
Reviewed-by: Daniel Charles <daniel.charles@intel.com>
>
> drivers/gpu/drm/xe/xe_gt_debugfs.c | 26 ++++++++
> drivers/gpu/drm/xe/xe_hw_engine.c | 3 +
> drivers/gpu/drm/xe/xe_lrc.c | 96 +++++++++++++++++++++++++++
> drivers/gpu/drm/xe/xe_lrc.h | 4 ++
> drivers/gpu/drm/xe/xe_reg_sr.c | 71 +++++++++++++++++++-
> drivers/gpu/drm/xe/xe_reg_sr.h | 7 ++
> drivers/gpu/drm/xe/xe_reg_whitelist.c | 3 +
> drivers/gpu/drm/xe/xe_tuning.c | 7 ++
> drivers/gpu/drm/xe/xe_wa.c | 6 ++
> 9 files changed, 221 insertions(+), 2 deletions(-)
>
prev parent reply other threads:[~2026-02-23 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 0:09 [PATCH v3 0/4] Add debugfs facility to catch RTP mistakes Matt Roper
2026-02-13 0:09 ` [PATCH v3 1/4] drm/xe/reg_sr: Don't process gt/hwe lists in VF Matt Roper
2026-02-17 21:34 ` Dixit, Ashutosh
2026-02-13 0:09 ` [PATCH v3 2/4] drm/xe/reg_sr: Add debugfs to verify status of reg_sr programming Matt Roper
2026-02-13 0:09 ` [PATCH v3 3/4] drm/xe: Add facility to lookup the value of a register in a default LRC Matt Roper
2026-02-13 0:09 ` [PATCH v3 4/4] drm/xe/reg_sr: Allow register_save_restore_check debugfs to verify LRC values Matt Roper
2026-02-13 0:16 ` ✓ CI.KUnit: success for Add debugfs facility to catch RTP mistakes (rev2) Patchwork
2026-02-13 0:59 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-14 1:07 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-23 17:40 ` Daniel Charles [this message]
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=02b09764-52db-4b81-aa31-37e588953a0e@intel.com \
--to=daniel.charles@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@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