| author | Suman Anna <s-anna@ti.com> | |
| Fri, 28 Apr 2017 21:46:12 +0000 (16:46 -0500) | ||
| committer | Suman Anna <s-anna@ti.com> | |
| Mon, 11 Mar 2019 16:59:48 +0000 (11:59 -0500) | ||
| commit | 10f1ce98200ec692c9c6381814a551abe20e27e2 | |
| tree | 09b22532fbd263ef1f79f74b88722d7420d1e79c | tree | snapshot (tar.xz tar.gz zip) |
| parent | 418ad4b211e9723bc6344167543f98f0fe5944ab | commit | diff |
remoteproc: implement last trace for remoteproc
The last trace is a way of preserving the remoteproc traces past
remoteproc recovery. This is achieved by creating a new traceY_last
debugfs entry during a crash for each trace entry, and copying the
trace buffer contents into the corresponding last trace entry. This
copied contents can then be read out using a debugfs entry. The
trace entries themselves are cleaned up after the copy and are
recreated during a recovery reload.
Eg:
cat <debugfs_root>/remoteproc/remoteprocX/traceY_last
should give the traces that were printed out just before the recovery
happened on remoteproc X for trace Y.
Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
The last trace is a way of preserving the remoteproc traces past
remoteproc recovery. This is achieved by creating a new traceY_last
debugfs entry during a crash for each trace entry, and copying the
trace buffer contents into the corresponding last trace entry. This
copied contents can then be read out using a debugfs entry. The
trace entries themselves are cleaned up after the copy and are
recreated during a recovery reload.
Eg:
cat <debugfs_root>/remoteproc/remoteprocX/traceY_last
should give the traces that were printed out just before the recovery
happened on remoteproc X for trace Y.
Signed-off-by: Subramaniam Chanderashekarapuram <subramaniam.ca@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
| drivers/remoteproc/remoteproc_core.c | diff | blob | history | |
| include/linux/remoteproc.h | diff | blob | history |