Thread (12 messages) 12 messages, 4 authors, 2017-08-23

[PATCH 00/17] coresight: next v4.12-rc4

STALE3327d

From: Suzuki.Poulose@arm.com (Suzuki K Poulose)
Date: 2017-06-15 13:08:09

Revision v1 of 2 in this series.

Revisions (2)
  1. v1 current
  2. v1 [diff vs current]
On 14/06/17 07:22, Leo Yan wrote:
Hi Kim,

On Tue, Jun 13, 2017 at 04:17:12PM -0500, Kim Phillips wrote:

[...]
quoted
quoted
quoted
Also, do the current juno platforms not have CPU debug modules?  I'd
like to test the new driver.
By all means - Leo pointed out the patch adding the CPU debug entries in
the DT  file for Juno.
Thanks, I applied it, was able to
toggle /sys/kernel/debug/coresight_cpu_debug/enable, but wasn't sure
how to trigger the cpu debug output...
You could trigger panic flow with command, then can see CPU debug output:
echo c > /proc/sysrq-trigger
I think, may be we should provide a handle to trigger the CPU debug dump
manually, rather than using it only for panic. Something like :

echo 1 > /sys/kernel/debug/coresight_cpu_debug/trigger

Thoughts ?

Suzuki
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help