From: Matthew Auld <matthew.auld@intel.com>
To: himanshu.girotra@intel.com, igt-dev@lists.freedesktop.org
Cc: matthew.d.roper@intel.com, francois.dugast@intel.com
Subject: Re: [PATCH i-g-t] lib/intel_pat: add hardcoded PAT fallback for older kernels
Date: Fri, 27 Mar 2026 10:35:31 +0000 [thread overview]
Message-ID: <02d78ecd-215b-43a7-ba0a-b58bfe34b8d0@intel.com> (raw)
In-Reply-To: <20260327052212.27431-1-himanshu.girotra@intel.com>
On 27/03/2026 05:22, himanshu.girotra@intel.com wrote:
> From: Himanshu Girotra <himanshu.girotra@intel.com>
>
> When IGT runs on kernels that lack the gt0/pat_sw_config debugfs entry
> (commit "drm/xe: expose PAT software config to debugfs"), the PAT cache
> is NULL and intel_get_pat_idx() hits a fatal assertion. This breaks
> basic tests like xe_exec_basic on stock distro kernels (e.g. Ubuntu
> 25.10).
>
> Add xe_pat_fallback() with hardcoded PAT indices matching the kernel's
> xe_pat_init_early() for platforms up to Crescent Island (xe3p XPC).
> When the debugfs is unavailable, the fallback provides correct values
> instead of crashing. Newer platforms (xe3p LPG and beyond) are not
> covered because their kernel support arrived after the debugfs entry
> was already in place.
>
> Cc: Matthew Auld <matthew.auld@intel.com>
> Cc: Matt Roper <matthew.d.roper@intel.com>
> Cc: Francois Dugast <francois.dugast@intel.com>
> Signed-off-by: Himanshu Girotra <himanshu.girotra@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
next prev parent reply other threads:[~2026-03-27 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 5:22 [PATCH i-g-t] lib/intel_pat: add hardcoded PAT fallback for older kernels himanshu.girotra
2026-03-27 6:28 ` ✓ i915.CI.BAT: success for " Patchwork
2026-03-27 6:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-03-27 10:35 ` Matthew Auld [this message]
2026-03-27 22:07 ` ✓ Xe.CI.FULL: " Patchwork
2026-03-28 7:31 ` ✗ i915.CI.Full: failure " Patchwork
2026-03-31 22:56 ` [PATCH i-g-t] " Dixit, Ashutosh
2026-03-31 23:06 ` Dixit, Ashutosh
2026-04-01 0:10 ` Wang, X
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=02d78ecd-215b-43a7-ba0a-b58bfe34b8d0@intel.com \
--to=matthew.auld@intel.com \
--cc=francois.dugast@intel.com \
--cc=himanshu.girotra@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=matthew.d.roper@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