From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Upadhyay, Tejas" <tejas.upadhyay@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for drm/xe: cancel pending job timer before freeing scheduler
Date: Mon, 24 Feb 2025 14:28:54 -0000 [thread overview]
Message-ID: <174040733454.1618220.4877984374163452483@b555e5b46a47> (raw)
In-Reply-To: <20250224122237.576893-1-tejas.upadhyay@intel.com>
== Series Details ==
Series: drm/xe: cancel pending job timer before freeing scheduler
URL : https://patchwork.freedesktop.org/series/145308/
State : success
== Summary ==
+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
22f9cda3436b4fe965b5c5f31d2f2c1bcb483189
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit e5129831e106671216aa85a425a35109db624a81
Author: Tejas Upadhyay <tejas.upadhyay@intel.com>
Date: Mon Feb 24 17:52:37 2025 +0530
drm/xe: cancel pending job timer before freeing scheduler
Async call to __guc_exec_queue_fini_async frees scheduler
at the same time when some scheduler submission would have
timed out and restarted. To handle such small window race
case, all pending jobs timer should be cancelled before
freeing scheduler.
It will help to solve below which is not easily reproducible,
https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/4223
V2(MattB):
- Cancel pending jobs before scheduler finish
Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>
+ /mt/dim checkpatch be5a404c3344b7d794766f045b8f94aa93c42069 drm-intel
e5129831e106 drm/xe: cancel pending job timer before freeing scheduler
next prev parent reply other threads:[~2025-02-24 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-24 12:22 [PATCH] drm/xe: cancel pending job timer before freeing scheduler Tejas Upadhyay
2025-02-24 14:28 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-24 14:28 ` Patchwork [this message]
2025-02-24 14:30 ` ✓ CI.KUnit: " Patchwork
2025-02-24 14:46 ` ✓ CI.Build: " Patchwork
2025-02-24 14:48 ` ✓ CI.Hooks: " Patchwork
2025-02-24 14:50 ` ✓ CI.checksparse: " Patchwork
2025-02-24 14:51 ` [PATCH] " Matthew Brost
2025-02-24 15:10 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-02-24 16:26 ` ✗ Xe.CI.Full: " 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=174040733454.1618220.4877984374163452483@b555e5b46a47 \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=tejas.upadhyay@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