From: sashiko-bot@kernel.org
To: "Krzysztof Niemiec" <krzysztof.niemiec@intel.com>,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Subject: Re: [RFC 2/5] drm/i915/selftests: Port GT-dependent selftests to work with multi-GT (low-hanging fruits part 2)
Date: Thu, 29 Oct 2026 01:56:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-188625@kernel.org> (raw)
In-Reply-To: <20261029014155.55865-3-krzysztof.niemiec@intel.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] drm/i915/selftests: unported wedged check in i915_request_live_selftests()
--
commit 46c0aca503dcff6d10a11b75ac8ca3cd05b6385a
Author: Krzysztof Niemiec <krzysztof.niemiec@intel.com>
drm/i915/selftests: Port GT-dependent selftests to work with multi-GT (low-hanging fruits part 2)
This commit updates top-level i915 selftest entry points that do not take a GT
directly to check all GTs via for_each_gt() and abort if any GT is wedged.
[ ... ]
> diff --git a/drivers/gpu/drm/i915/selftests/i915_request.c b/drivers/gpu/drm/i915/selftests/i915_request.c
> index e1a7c454a0a9d..6bf8ba4744974 100644
> --- a/drivers/gpu/drm/i915/selftests/i915_request.c
> +++ b/drivers/gpu/drm/i915/selftests/i915_request.c
> @@ -3295,9 +3295,13 @@ int i915_request_perf_selftests(struct drm_i915_private *i915)
> SUBTEST(perf_series_engines),
> SUBTEST(perf_parallel_engines),
> };
> + struct intel_gt *gt;
> + unsigned int id;
>
> - if (intel_gt_is_wedged(to_gt(i915)))
> - return 0;
> + for_each_gt(gt, i915, id) {
> + if (intel_gt_is_wedged(gt))
> + return 0;
> + }
[Severity: Medium]
Should i915_request_live_selftests() in
drivers/gpu/drm/i915/selftests/i915_request.c also be updated to iterate over
all GTs with for_each_gt() like i915_request_perf_selftests() here and
intel_memory_region_live_selftests() in
drivers/gpu/drm/i915/selftests/intel_memory_region.c?
Currently, i915_request_live_selftests() still checks only the primary GT:
int i915_request_live_selftests(struct drm_i915_private *i915)
{
...
if (intel_gt_is_wedged(to_gt(i915)))
return 0;
return i915_live_subtests(tests, i915);
}
Its subtests (such as live_nop_request(), live_all_engines(),
live_sequential_engines(), and live_parallel_engines()) do not reference
to_gt(i915) and instead iterate across all UABI engines on all GTs via
for_each_uabi_engine(), finishing with igt_live_test_end() ->
igt_flush_test().
If a secondary GT is wedged while GT0 is healthy,
i915_request_live_selftests() will not skip and will instead run against the
wedged GT's engines and fail with -EIO in igt_flush_test().
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261029014155.55865-1-krzysztof.niemiec@intel.com?part=2
next prev parent reply other threads:[~2026-10-29 1:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-29 1:41 [RFC 0/5] Selftests fixes for multi-gt platforms in i915 Krzysztof Niemiec
2026-10-29 1:41 ` [RFC 1/5] drm/i915/selftests: Port GT-dependent selftests to work with multi-GT (low-hanging fruits part 1) Krzysztof Niemiec
2026-10-29 2:09 ` sashiko-bot
2026-10-29 1:41 ` [RFC 2/5] drm/i915/selftests: Port GT-dependent selftests to work with multi-GT (low-hanging fruits part 2) Krzysztof Niemiec
2026-10-29 1:56 ` sashiko-bot [this message]
2026-10-29 1:41 ` [RFC 3/5] drm/i915/selftests: Port i915_gem_gtt.c selftest file to multi-gt Krzysztof Niemiec
2026-10-29 1:41 ` [RFC 4/5] drm/i915/sefltests: Port i915_gem_context.c " Krzysztof Niemiec
2026-10-29 1:41 ` [RFC 5/5] drm/i915/selftests: Port selftests that access ggtt to work with multi-gt Krzysztof Niemiec
2026-10-29 1:51 ` sashiko-bot
2026-10-29 2:40 ` ✗ i915.CI.BAT: failure for Selftests fixes for multi-gt platforms in i915 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=sashiko-outbox-188625@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=krzysztof.niemiec@intel.com \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.