From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Badal Nilawar" <badal.nilawar@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: ✓ CI.checkpatch: success for Workaround to handle G2H timeout (rev2)
Date: Thu, 17 Oct 2024 11:15:47 -0000 [thread overview]
Message-ID: <172916374712.1278402.7012173421574433722@2413ebb6fbb6> (raw)
In-Reply-To: <20241017111410.2553784-1-badal.nilawar@intel.com>
== Series Details ==
Series: Workaround to handle G2H timeout (rev2)
URL : https://patchwork.freedesktop.org/series/140056/
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
30ab6715fc09baee6cc14cb3c89ad8858688d474
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 79103aa49c7ace52dfd32fa4f5d40ee8983a21b9
Author: Badal Nilawar <badal.nilawar@intel.com>
Date: Thu Oct 17 16:44:10 2024 +0530
drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout
In case if g2h worker doesn't get opportunity to within specified
timeout delay then flush the g2h worker explicitly.
v2:
- Describe change in the comment and add TODO (Matt B/John H)
- Add xe_gt_warn on fence done after G2H flush (John H)
v3:
- Updated the comment with root cause
- Clean up xe_gt_warn message (John H)
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1620
Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/2902
Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
Cc: Matthew Brost <matthew.brost@intel.com>
Cc: Matthew Auld <matthew.auld@intel.com>
Cc: John Harrison <John.C.Harrison@Intel.com>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
+ /mt/dim checkpatch 81420006f741f9783adea6ab5620ce54697f1b20 drm-intel
79103aa49c7a drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout
next prev parent reply other threads:[~2024-10-17 11:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 11:14 [PATCH v3 0/1] Workaround to handle G2H timeout Badal Nilawar
2024-10-17 11:14 ` [PATCH v3 1/1] drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout Badal Nilawar
2024-10-17 13:43 ` Ghimiray, Himal Prasad
2024-10-17 15:17 ` Matthew Brost
2024-10-18 0:05 ` John Harrison
2024-10-17 11:15 ` ✓ CI.Patch_applied: success for Workaround to handle G2H timeout (rev2) Patchwork
2024-10-17 11:15 ` Patchwork [this message]
2024-10-17 11:16 ` ✓ CI.KUnit: " Patchwork
2024-10-17 11:28 ` ✓ CI.Build: " Patchwork
2024-10-17 11:30 ` ✓ CI.Hooks: " Patchwork
2024-10-17 11:32 ` ✓ CI.checksparse: " Patchwork
2024-10-17 22:36 ` ✗ CI.FULL: failure " Patchwork
2024-10-18 3:49 ` ✓ CI.BAT: success " 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=172916374712.1278402.7012173421574433722@2413ebb6fbb6 \
--to=patchwork@emeril.freedesktop.org \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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