Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bnilawar <badal.nilawar@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, john.c.harrison@intel.com
Subject: [[CI] 00/12] Debug g2h timeout issue
Date: Fri, 20 Sep 2024 19:36:34 +0530	[thread overview]
Message-ID: <20240920140646.618008-1-badal.nilawar@intel.com> (raw)

Do not review

John Harrison (10):
  drm/xe/guc: Remove spurious line feed in debug print
  drm/xe/devcoredump: Use drm_puts and already cached local variables
  drm/xe/devcoredump: Improve section headings and add tile info
  drm/xe/devcoredump: Add ASCII85 dump helper function
  drm/xe/guc: Copy GuC log prior to dumping
  drm/xe/guc: Use a two stage dump for GuC logs and add more info
  drm/xe/guc: Dead CT helper
  drm/xe/guc: Dump entire CTB on errors
  drm/xe/guc: Add GuC log to devcoredump captures
  drm/xe/guc: Add a helper function for dumping GuC log to dmesg

Michal Wajdeczko (1):
  drm/print: Introduce drm_line_printer

bnilawar (1):
  [For CI] Debug prints/logs to debug G2H timeout issue

 drivers/gpu/drm/drm_print.c                   |  14 +
 .../drm/xe/abi/guc_communication_ctb_abi.h    |   1 +
 drivers/gpu/drm/xe/regs/xe_guc_regs.h         |   1 +
 drivers/gpu/drm/xe/xe_devcoredump.c           | 144 +++++-
 drivers/gpu/drm/xe/xe_devcoredump.h           |   6 +
 drivers/gpu/drm/xe/xe_devcoredump_types.h     |  13 +-
 drivers/gpu/drm/xe/xe_device.c                |   1 +
 drivers/gpu/drm/xe/xe_guc.c                   |   6 +-
 drivers/gpu/drm/xe/xe_guc_ct.c                | 416 ++++++++++++++----
 drivers/gpu/drm/xe/xe_guc_ct.h                |  10 +-
 drivers/gpu/drm/xe/xe_guc_ct_types.h          |  29 +-
 drivers/gpu/drm/xe/xe_guc_log.c               | 208 ++++++++-
 drivers/gpu/drm/xe/xe_guc_log.h               |   5 +
 drivers/gpu/drm/xe/xe_guc_log_types.h         |  27 ++
 drivers/gpu/drm/xe/xe_guc_submit.c            |   2 +-
 drivers/gpu/drm/xe/xe_hw_engine.c             |   1 -
 include/drm/drm_print.h                       |  64 +++
 17 files changed, 804 insertions(+), 144 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-09-20 13:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-20 14:06 bnilawar [this message]
2024-09-20 14:06 ` [[CI] 01/12] drm/xe/guc: Remove spurious line feed in debug print bnilawar
2024-09-20 14:06 ` [[CI] 02/12] drm/xe/devcoredump: Use drm_puts and already cached local variables bnilawar
2024-09-20 14:06 ` [[CI] 03/12] drm/xe/devcoredump: Improve section headings and add tile info bnilawar
2024-09-20 14:06 ` [[CI] 04/12] drm/xe/devcoredump: Add ASCII85 dump helper function bnilawar
2024-09-20 14:06 ` [[CI] 05/12] drm/xe/guc: Copy GuC log prior to dumping bnilawar
2024-09-20 14:06 ` [[CI] 06/12] drm/xe/guc: Use a two stage dump for GuC logs and add more info bnilawar
2024-09-20 14:06 ` [[CI] 07/12] drm/print: Introduce drm_line_printer bnilawar
2024-09-20 14:06 ` [[CI] 08/12] drm/xe/guc: Dead CT helper bnilawar
2024-09-20 14:06 ` [[CI] 09/12] drm/xe/guc: Dump entire CTB on errors bnilawar
2024-09-20 14:06 ` [[CI] 10/12] drm/xe/guc: Add GuC log to devcoredump captures bnilawar
2024-09-20 14:06 ` [[CI] 11/12] drm/xe/guc: Add a helper function for dumping GuC log to dmesg bnilawar
2024-09-20 14:06 ` [[CI] 12/12] [For CI] Debug prints/logs to debug G2H timeout issue bnilawar
2024-09-20 14:43 ` ✓ CI.Patch_applied: success for 10/12] drm/xe/guc: Add GuC log to devcoredump captures Patchwork
2024-09-20 14:43 ` ✓ CI.checkpatch: " Patchwork
2024-09-20 14:44 ` ✓ CI.KUnit: " Patchwork
2024-09-20 14:56 ` ✓ CI.Build: " Patchwork
2024-09-20 14:58 ` ✓ CI.Hooks: " Patchwork
2024-09-20 15:00 ` ✓ CI.checksparse: " Patchwork
2024-09-20 15:18 ` ✓ CI.BAT: " Patchwork
2024-09-20 20:37 ` ✗ CI.FULL: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-09-20 14:29 [CI 00/12] Debug g2h timeout issue Badal Nilawar
2024-09-20 14:48 ` Jani Nikula
2024-09-23 19:45   ` John Harrison
2024-09-26 18:55     ` Rodrigo Vivi
2024-09-27 17:50       ` Nilawar, Badal

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=20240920140646.618008-1-badal.nilawar@intel.com \
    --to=badal.nilawar@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=john.c.harrison@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