From: sai.gowtham.ch@intel.com
To: igt-dev@lists.freedesktop.org, sai.gowtham.ch@intel.com
Subject: [PATCH 0/2] Extend intel_error_decode tool to work with xe
Date: Fri, 31 Jan 2025 20:29:38 +0000 [thread overview]
Message-ID: <20250131202940.1124460-1-sai.gowtham.ch@intel.com> (raw)
From: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
This Series has changes of lib support of error dumps decode for xe,
intel_error_decode_xe has wrappers which reads the xe dumps and prints
details of the error dumps, just like we had for i915.
These libs had being extended in existing intel_error_decode tool, to
make them work for decoding of xe dumps.
Signed-off-by: Sai Gowtham Ch <sai.gowtham.ch@intel.com>
Sai Gowtham Ch (2):
lib/xe/intel_error_decode_xe: error decode support for xe driver
tools/intel_error_decode: Enable support for xe driver in the tool
lib/meson.build | 1 +
lib/xe/intel_error_decode_xe.c | 287 +++++++++++++++++++++++++++++
lib/xe/intel_error_decode_xe_lib.h | 26 +++
tools/intel_error_decode.c | 156 +++++++++++-----
4 files changed, 421 insertions(+), 49 deletions(-)
create mode 100644 lib/xe/intel_error_decode_xe.c
create mode 100644 lib/xe/intel_error_decode_xe_lib.h
--
2.34.1
next reply other threads:[~2025-01-31 20:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 20:29 sai.gowtham.ch [this message]
2025-01-31 20:29 ` [PATCH 1/2] lib/xe/intel_error_decode_xe: error decode support for xe driver sai.gowtham.ch
2025-02-06 18:48 ` Rodrigo Vivi
2025-02-06 19:04 ` Souza, Jose
2025-02-11 5:35 ` Ch, Sai Gowtham
2025-02-11 13:21 ` Souza, Jose
2025-01-31 20:29 ` [PATCH 2/2] tools/intel_error_decode: Enable support for xe driver in the tool sai.gowtham.ch
2025-02-06 16:24 ` Rodrigo Vivi
2025-02-11 5:37 ` Ch, Sai Gowtham
2025-01-31 21:48 ` ✓ Xe.CI.BAT: success for Extend intel_error_decode tool to work with xe Patchwork
2025-01-31 21:49 ` ✓ i915.CI.BAT: " Patchwork
2025-02-01 5:27 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-01 12:15 ` ✗ i915.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=20250131202940.1124460-1-sai.gowtham.ch@intel.com \
--to=sai.gowtham.ch@intel.com \
--cc=igt-dev@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