From: Badal Nilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, john.c.harrison@intel.com,
himal.prasad.ghimiray@intel.com, rodrigo.vivi@intel.com,
matthew.brost@intel.com, matthew.auld@intel.com
Subject: [PATCH v3 0/1] Workaround to handle G2H timeout
Date: Thu, 17 Oct 2024 16:44:09 +0530 [thread overview]
Message-ID: <20241017111410.2553784-1-badal.nilawar@intel.com> (raw)
Patches in this series are for temporary workaround to handle
G2H timeout seen due to delays in workqueue scheduling on Lunarlake
platform.
Issue can be seen while running xe_pm tests and xe_freq_freq@freq_reset_multiple test
in continuous loop
Badal Nilawar (1):
drm/xe/guc/ct: Flush g2h worker in case of g2h response timeout
drivers/gpu/drm/xe/xe_guc_ct.c | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
--
2.34.1
next reply other threads:[~2024-10-17 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 11:14 Badal Nilawar [this message]
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 ` ✓ CI.checkpatch: " Patchwork
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=20241017111410.2553784-1-badal.nilawar@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.brost@intel.com \
--cc=rodrigo.vivi@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