From: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: alsa-devel@alsa-project.org,
pierre-louis.bossart@linux.intel.com,
ranjani.sridharan@linux.intel.com, kai.vehmanen@linux.intel.com,
rander.wang@intel.com, guennadi.liakhovetski@linux.intel.com
Subject: [PATCH 0/9] ASoC: SOF: ipc4/Intel: Support for firmware exception handling
Date: Tue, 19 Sep 2023 12:24:07 +0300 [thread overview]
Message-ID: <20230919092416.4137-1-peter.ujfalusi@linux.intel.com> (raw)
Hi,
When a firmware crashes it creats a panic information into a telemetry slot.
The panic format is defined by Zephyr, includes stack and additional information
to help to identify the reason for the crash.
Part of the firmware exception handling the firmware also sends an
EXCEPTION_CAUGHT notification.
This series implements the kernel side handling of the exception:
print information into the kernel log
export the whole telemetry slot to user space for tools extract additional
information from the panic dump.
Regards,
Peter
---
Rander Wang (9):
ASoC: SOF: Xtensa: dump ar registers to restore call stack
ASoC: SOF: ipc4-mtrace: move debug slot related definitions to
header.h
ASoC: SOF: ipc4: add a helper function to search debug slot
ASoC: SOF: ipc4: add definition of telemetry slot for exception
handling
ASoC: SOF: ipc4: add exception node in sof debugfs directory
ASoC: SOF: Intel: add telemetry retrieval support on Intel platforms
ASoC: SOF: Intel: mtl: dump dsp stack
ASoC: SOF: Intel: hda: add ipc4 FW panic support on CAVS 2.5+
platforms
ASoC: SOF: ipc4: handle EXCEPTION_CAUGHT notification from firmware
include/sound/sof/ipc4/header.h | 17 ++++++
sound/soc/sof/Makefile | 2 +-
sound/soc/sof/intel/Makefile | 3 +-
sound/soc/sof/intel/hda.c | 14 +++++
sound/soc/sof/intel/hda.h | 1 +
sound/soc/sof/intel/mtl.c | 3 ++
sound/soc/sof/intel/telemetry.c | 95 +++++++++++++++++++++++++++++++++
sound/soc/sof/intel/telemetry.h | 35 ++++++++++++
sound/soc/sof/intel/tgl.c | 1 +
sound/soc/sof/ipc4-mtrace.c | 34 ++++--------
sound/soc/sof/ipc4-priv.h | 3 ++
sound/soc/sof/ipc4-telemetry.c | 95 +++++++++++++++++++++++++++++++++
sound/soc/sof/ipc4-telemetry.h | 73 +++++++++++++++++++++++++
sound/soc/sof/ipc4.c | 29 ++++++++++
sound/soc/sof/xtensa/core.c | 11 ++++
15 files changed, 391 insertions(+), 25 deletions(-)
create mode 100644 sound/soc/sof/intel/telemetry.c
create mode 100644 sound/soc/sof/intel/telemetry.h
create mode 100644 sound/soc/sof/ipc4-telemetry.c
create mode 100644 sound/soc/sof/ipc4-telemetry.h
--
2.42.0
next reply other threads:[~2023-09-19 9:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 9:24 Peter Ujfalusi [this message]
2023-09-19 9:24 ` [PATCH 1/9] ASoC: SOF: Xtensa: dump ar registers to restore call stack Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 2/9] ASoC: SOF: ipc4-mtrace: move debug slot related definitions to header.h Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 3/9] ASoC: SOF: ipc4: add a helper function to search debug slot Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 4/9] ASoC: SOF: ipc4: add definition of telemetry slot for exception handling Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 5/9] ASoC: SOF: ipc4: add exception node in sof debugfs directory Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 6/9] ASoC: SOF: Intel: add telemetry retrieval support on Intel platforms Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 7/9] ASoC: SOF: Intel: mtl: dump dsp stack Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 8/9] ASoC: SOF: Intel: hda: add ipc4 FW panic support on CAVS 2.5+ platforms Peter Ujfalusi
2023-09-19 9:24 ` [PATCH 9/9] ASoC: SOF: ipc4: handle EXCEPTION_CAUGHT notification from firmware Peter Ujfalusi
2023-09-21 16:30 ` [PATCH 0/9] ASoC: SOF: ipc4/Intel: Support for firmware exception handling Mark Brown
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=20230919092416.4137-1-peter.ujfalusi@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=guennadi.liakhovetski@linux.intel.com \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=rander.wang@intel.com \
--cc=ranjani.sridharan@linux.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