From: Jani Nikula <jani.nikula@linux.intel.com>
To: Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Karas <krzysztof.karas@intel.com>,
intel-gfx@lists.freedesktop.org
Cc: Andi Shyti <andi.shyti@linux.intel.com>,
Janusz Krzysztofik <janusz.krzysztofik@linux.intel.com>,
Sebastian Brzezinka <sebastian.brzezinka@intel.com>,
Krzysztof Niemiec <krzysztof.niemiec@intel.com>
Subject: Re: [PATCH] drm/i915/gt: Do not destroy uninitialized timer
Date: Tue, 29 Sep 2026 15:43:54 +0300 [thread overview]
Message-ID: <890f98a19e790ab09feb3b990330cd52d82a68c2@intel.com> (raw)
In-Reply-To: <DLRRUM4IIQX2.2AYNTH45B6AF0@intel.com>
On Tue, 29 Sep 2026, Sebastian Brzezinka <sebastian.brzezinka@intel.com> wrote:
> Hi Krzysztof,
>
> On Tue Sep 29, 2026 at 1:12 PM CEST, Krzysztof Karas wrote:
>> If intel_ring_begin() fails in live_emit_pte_full_ring(), then
>> cleanup is performed on an uninitialized timer.
>>
>> Check if the timer has been set up, before trying to remove it.
>>
>> Assisted-by: Copilot-Claude-Opus-5
>> Signed-off-by: Krzysztof Karas <krzysztof.karas@intel.com>
>> ---
> How about something like this:
That makes no sense.
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_migrate.c b/drivers/gpu/drm/i915/gt/selftest_migrate.c
> index 5b986a7687d9..7efdc8d9d8cd 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_migrate.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_migrate.c
> @@ -626,7 +626,8 @@ static int live_emit_pte_full_ring(void *arg)
> cs = intel_ring_begin(rq, sz);
> if (IS_ERR(cs)) {
> err = PTR_ERR(cs);
> - goto out_rq;
> + i915_request_add(rq);
> + goto out_unpin;
> }
>
> memset32(cs, MI_NOOP, sz);
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-09-29 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 11:12 [PATCH] drm/i915/gt: Do not destroy uninitialized timer Krzysztof Karas
2026-09-29 11:19 ` Jani Nikula
2026-09-29 11:42 ` Sebastian Brzezinka
2026-09-29 12:43 ` Jani Nikula [this message]
2026-09-29 13:26 ` ✓ i915.CI.BAT: success for " Patchwork
2026-09-29 16:58 ` ✗ i915.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=890f98a19e790ab09feb3b990330cd52d82a68c2@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=andi.shyti@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=janusz.krzysztofik@linux.intel.com \
--cc=krzysztof.karas@intel.com \
--cc=krzysztof.niemiec@intel.com \
--cc=sebastian.brzezinka@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 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.