* coresight: documentation: update sysfs section
@ 2018-05-07 22:29 ` Kim Phillips
0 siblings, 0 replies; 30+ messages in thread
From: Kim Phillips @ 2018-05-07 22:29 UTC (permalink / raw)
To: Mathieu Poirier
Cc: Jonathan Corbet, linux-arm-kernel, linux-doc, linux-kernel
- Align and show updated ls devices output from the TC2, based on
current driver
- Provide an example from an ETMv4 based system (Juno)
- Reflect changes to the way the RAM write pointer is accessed since
it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS
management entries").
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Jonathan Corbet <corbet@lwn.net>
Signed-off-by: Kim Phillips <kim.phillips@arm.com>
---
Documentation/trace/coresight.txt | 40 ++++++++++++++++++-------------
1 file changed, 24 insertions(+), 16 deletions(-)
diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt
index 6f0120c3a4f1..d23d6354b372 100644
--- a/Documentation/trace/coresight.txt
+++ b/Documentation/trace/coresight.txt
@@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will
show up under /sys/bus/coresight/devices, as showns here for a TC2 platform:
root:~# ls /sys/bus/coresight/devices/
-replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm
-20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm
+20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator
+20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm
root:~#
+and here for a Juno platform:
+
+root@juno:~# ls /sys/bus/coresight/devices/
+20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel
+20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm
+20040000.funnel 20140000.etf 22140000.etm 23240000.etm
+20070000.etr 20150000.funnel 23040000.etm 23340000.etm
+root@juno:~#
+
+Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB.
+
The functions take a "struct coresight_device", which looks like this:
struct coresight_desc {
@@ -193,16 +204,16 @@ the information carried in "THIS_MODULE".
How to use the tracer modules
-----------------------------
-Before trace collection can start, a coresight sink needs to be identify.
+Before trace collection can start, a coresight sink needs to be identified.
There is no limit on the amount of sinks (nor sources) that can be enabled at
any given moment. As a generic operation, all device pertaining to the sink
class will have an "active" entry in sysfs:
root:/sys/bus/coresight/devices# ls
-replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm
-20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm
+20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator
+20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm
root:/sys/bus/coresight/devices# ls 20010000.etb
-enable_sink status trigger_cntr
+enable_sink mgmt power subsystem trigger_cntr uevent
root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink
root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink
1
@@ -216,16 +227,13 @@ trigger a trace capture:
root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source
root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source
1
-root:/sys/bus/coresight/devices# cat 20010000.etb/status
-Depth: 0x2000
-Status: 0x1
-RAM read ptr: 0x0
-RAM wrt ptr: 0x19d3 <----- The write pointer is moving
-Trigger cnt: 0x0
-Control: 0x1
-Flush status: 0x0
-Flush ctrl: 0x2001
-root:/sys/bus/coresight/devices#
+
+Observe the write pointer moving:
+
+root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp
+0x1a8
+root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp
+0x19a6
Trace collection is stopped the same way:
--
2.17.0
^ permalink raw reply related [flat|nested] 30+ messages in thread* coresight: documentation: update sysfs section @ 2018-05-07 22:29 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-07 22:29 UTC (permalink / raw) To: linux-arm-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- Documentation/trace/coresight.txt | 40 ++++++++++++++++++------------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..d23d6354b372 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root at juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root at juno:~# + +Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +204,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +227,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply related [flat|nested] 30+ messages in thread
* coresight: documentation: update sysfs section @ 2018-05-07 22:29 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-07 22:29 UTC (permalink / raw) To: Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, linux-doc, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- Documentation/trace/coresight.txt | 40 ++++++++++++++++++------------- 1 file changed, 24 insertions(+), 16 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..d23d6354b372 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +204,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +227,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: coresight: documentation: update sysfs section 2018-05-07 22:29 ` Kim Phillips (?) @ 2018-05-08 15:35 ` Mathieu Poirier -1 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-08 15:35 UTC (permalink / raw) To: Kim Phillips Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 7 May 2018 at 16:29, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > Documentation/trace/coresight.txt | 40 ++++++++++++++++++------------- > 1 file changed, 24 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..d23d6354b372 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will > show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB. The above is not entirely correct. On Juno users can select the ETF, ETR and TPIU as a sink target while on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +204,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +227,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > ^ permalink raw reply [flat|nested] 30+ messages in thread
* coresight: documentation: update sysfs section @ 2018-05-08 15:35 ` Mathieu Poirier 0 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-08 15:35 UTC (permalink / raw) To: linux-arm-kernel On 7 May 2018 at 16:29, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > Documentation/trace/coresight.txt | 40 ++++++++++++++++++------------- > 1 file changed, 24 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..d23d6354b372 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will > show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root at juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root at juno:~# > + > +Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB. The above is not entirely correct. On Juno users can select the ETF, ETR and TPIU as a sink target while on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +204,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +227,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: coresight: documentation: update sysfs section @ 2018-05-08 15:35 ` Mathieu Poirier 0 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-08 15:35 UTC (permalink / raw) To: Kim Phillips Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 7 May 2018 at 16:29, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > Documentation/trace/coresight.txt | 40 ++++++++++++++++++------------- > 1 file changed, 24 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..d23d6354b372 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,21 @@ If everything goes well during the registration process the new devices will > show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note the Juno uses an Embedded Trace Router (ETR) instead of an ETB. The above is not entirely correct. On Juno users can select the ETF, ETR and TPIU as a sink target while on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +204,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +227,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section 2018-05-08 15:35 ` Mathieu Poirier (?) @ 2018-05-14 17:19 ` Kim Phillips -1 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 17:19 UTC (permalink / raw) To: Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -144,10 +144,22 @@ If everything goes well during the registration process the new devices will show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-14 17:19 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 17:19 UTC (permalink / raw) To: linux-arm-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -144,10 +144,22 @@ If everything goes well during the registration process the new devices will show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root at juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root at juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-14 17:19 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 17:19 UTC (permalink / raw) To: Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -144,10 +144,22 @@ If everything goes well during the registration process the new devices will show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section 2018-05-14 17:19 ` Kim Phillips (?) @ 2018-05-14 18:54 ` Randy Dunlap -1 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 18:54 UTC (permalink / raw) To: Kim Phillips, Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 05/14/2018 10:19 AM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ > 1 file changed, 25 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt > b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d > 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,22 @@ If everything goes well during the registration > process the new devices will show up under /sys/bus/coresight/devices, > as showns here for a TC2 platform: as shown here > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm > 230c0000.funnel +20030000.tpiu 20130000.funnel > 220c0000.funnel 23140000.etm +20040000.funnel > 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm > 23340000.etm +root@juno:~# + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink > target while +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be > identify. +Before trace collection can start, a coresight sink needs to The - and + lines seems to be merged... > be identified. There is no limit on the amount of sinks (nor sources) > that can be enabled at any given moment. As a generic operation, all > device pertaining to the sink class will have an "active" entry in > sysfs: > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-14 18:54 ` Randy Dunlap 0 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 18:54 UTC (permalink / raw) To: linux-arm-kernel On 05/14/2018 10:19 AM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ > 1 file changed, 25 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt > b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d > 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,22 @@ If everything goes well during the registration > process the new devices will show up under /sys/bus/coresight/devices, > as showns here for a TC2 platform: as shown here > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:~# > > +and here for a Juno platform: > + > +root at juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm > 230c0000.funnel +20030000.tpiu 20130000.funnel > 220c0000.funnel 23140000.etm +20040000.funnel > 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm > 23340000.etm +root at juno:~# + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink > target while +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be > identify. +Before trace collection can start, a coresight sink needs to The - and + lines seems to be merged... > be identified. There is no limit on the amount of sinks (nor sources) > that can be enabled at any given moment. As a generic operation, all > device pertaining to the sink class will have an "active" entry in > sysfs: > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-14 18:54 ` Randy Dunlap 0 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 18:54 UTC (permalink / raw) To: Kim Phillips, Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 05/14/2018 10:19 AM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> > --- > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 41 +++++++++++++++++++------------ > 1 file changed, 25 insertions(+), 16 deletions(-) > > diff --git a/Documentation/trace/coresight.txt > b/Documentation/trace/coresight.txt index 6f0120c3a4f1..134994e9fa6d > 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -144,10 +144,22 @@ If everything goes well during the registration > process the new devices will show up under /sys/bus/coresight/devices, > as showns here for a TC2 platform: as shown here > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm > 230c0000.funnel +20030000.tpiu 20130000.funnel > 220c0000.funnel 23140000.etm +20040000.funnel > 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm > 23340000.etm +root@juno:~# + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink > target while +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be > identify. +Before trace collection can start, a coresight sink needs to The - and + lines seems to be merged... > be identified. There is no limit on the amount of sinks (nor sources) > that can be enabled at any given moment. As a generic operation, all > device pertaining to the sink class will have an "active" entry in > sysfs: > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > replicator +20030000.tpiu 2201c000.ptm 2203c000.etm > 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v3] coresight: documentation: update sysfs section 2018-05-14 18:54 ` Randy Dunlap (?) @ 2018-05-14 19:18 ` Kim Phillips -1 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 19:18 UTC (permalink / raw) To: Mathieu Poirier Cc: Randy Dunlap, Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-14 19:18 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 19:18 UTC (permalink / raw) To: linux-arm-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root at juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root at juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-14 19:18 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-14 19:18 UTC (permalink / raw) To: Mathieu Poirier Cc: Randy Dunlap, Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Mathieu Poirier <mathieu.poirier@linaro.org> Cc: Randy Dunlap <rdunlap@infradead.org> Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply related [flat|nested] 30+ messages in thread
* Re: [PATCH v3] coresight: documentation: update sysfs section 2018-05-14 19:18 ` Kim Phillips (?) @ 2018-05-14 21:03 ` Randy Dunlap -1 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 21:03 UTC (permalink / raw) To: Kim Phillips, Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 05/14/2018 12:18 PM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> FWIW: Acked-by: Randy Dunlap <rdunlap@infradead.org> Thanks. > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-14 21:03 ` Randy Dunlap 0 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 21:03 UTC (permalink / raw) To: linux-arm-kernel On 05/14/2018 12:18 PM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> FWIW: Acked-by: Randy Dunlap <rdunlap@infradead.org> Thanks. > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root at juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root at juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-14 21:03 ` Randy Dunlap 0 siblings, 0 replies; 30+ messages in thread From: Randy Dunlap @ 2018-05-14 21:03 UTC (permalink / raw) To: Kim Phillips, Mathieu Poirier Cc: Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On 05/14/2018 12:18 PM, Kim Phillips wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> FWIW: Acked-by: Randy Dunlap <rdunlap@infradead.org> Thanks. > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v3] coresight: documentation: update sysfs section 2018-05-14 19:18 ` Kim Phillips (?) @ 2018-05-15 16:00 ` Mathieu Poirier -1 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-15 16:00 UTC (permalink / raw) To: Kim Phillips Cc: Randy Dunlap, Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, Linux Kernel Mailing List On 14 May 2018 at 13:18, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> I'm good with this version - Jonathan, should I take this through my tree of you'll take care of it? In case of the former: Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-15 16:00 ` Mathieu Poirier 0 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-15 16:00 UTC (permalink / raw) To: linux-arm-kernel On 14 May 2018 at 13:18, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> I'm good with this version - Jonathan, should I take this through my tree of you'll take care of it? In case of the former: Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root at juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root at juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v3] coresight: documentation: update sysfs section @ 2018-05-15 16:00 ` Mathieu Poirier 0 siblings, 0 replies; 30+ messages in thread From: Mathieu Poirier @ 2018-05-15 16:00 UTC (permalink / raw) To: Kim Phillips Cc: Randy Dunlap, Jonathan Corbet, linux-arm-kernel, open list:DOCUMENTATION, Linux Kernel Mailing List On 14 May 2018 at 13:18, Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). > > Cc: Mathieu Poirier <mathieu.poirier@linaro.org> > Cc: Randy Dunlap <rdunlap@infradead.org> > Cc: Jonathan Corbet <corbet@lwn.net> > Signed-off-by: Kim Phillips <kim.phillips@arm.com> I'm good with this version - Jonathan, should I take this through my tree of you'll take care of it? In case of the former: Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> > --- > v3: address Randy Dunlap's showns->shown, corrected - and + line merging > v2: address Mathieu's comment about clarifying the sinks on the Juno > vs. TC2 platforms. > > Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ > 1 file changed, 26 insertions(+), 17 deletions(-) > > diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt > index 6f0120c3a4f1..15d2a0f1e1b8 100644 > --- a/Documentation/trace/coresight.txt > +++ b/Documentation/trace/coresight.txt > @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes > a reference to a "struct coresight_device", obtained at registration time. > > If everything goes well during the registration process the new devices will > -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: > +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: > > root:~# ls /sys/bus/coresight/devices/ > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:~# > > +and here for a Juno platform: > + > +root@juno:~# ls /sys/bus/coresight/devices/ > +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel > +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm > +20040000.funnel 20140000.etf 22140000.etm 23240000.etm > +20070000.etr 20150000.funnel 23040000.etm 23340000.etm > +root@juno:~# > + > +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while > +on TC2, the ETB and TPIU can be selected. > + > The functions take a "struct coresight_device", which looks like this: > > struct coresight_desc { > @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". > How to use the tracer modules > ----------------------------- > > -Before trace collection can start, a coresight sink needs to be identify. > +Before trace collection can start, a coresight sink needs to be identified. > There is no limit on the amount of sinks (nor sources) that can be enabled at > any given moment. As a generic operation, all device pertaining to the sink > class will have an "active" entry in sysfs: > > root:/sys/bus/coresight/devices# ls > -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm > +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator > +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm > root:/sys/bus/coresight/devices# ls 20010000.etb > -enable_sink status trigger_cntr > +enable_sink mgmt power subsystem trigger_cntr uevent > root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink > root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink > 1 > @@ -216,16 +228,13 @@ trigger a trace capture: > root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source > root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source > 1 > -root:/sys/bus/coresight/devices# cat 20010000.etb/status > -Depth: 0x2000 > -Status: 0x1 > -RAM read ptr: 0x0 > -RAM wrt ptr: 0x19d3 <----- The write pointer is moving > -Trigger cnt: 0x0 > -Control: 0x1 > -Flush status: 0x0 > -Flush ctrl: 0x2001 > -root:/sys/bus/coresight/devices# > + > +Observe the write pointer moving: > + > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x1a8 > +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp > +0x19a6 > > Trace collection is stopped the same way: > > -- > 2.17.0 > -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section 2018-05-14 17:19 ` Kim Phillips (?) @ 2018-05-16 19:18 ` Jonathan Corbet -1 siblings, 0 replies; 30+ messages in thread From: Jonathan Corbet @ 2018-05-16 19:18 UTC (permalink / raw) To: Kim Phillips Cc: Mathieu Poirier, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On Mon, 14 May 2018 12:19:59 -0500 Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). So I was going to apply this, but it's been pretty badly corrupted by your mailer. Could I ask you to retry, please? Thanks, jon ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-16 19:18 ` Jonathan Corbet 0 siblings, 0 replies; 30+ messages in thread From: Jonathan Corbet @ 2018-05-16 19:18 UTC (permalink / raw) To: linux-arm-kernel On Mon, 14 May 2018 12:19:59 -0500 Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). So I was going to apply this, but it's been pretty badly corrupted by your mailer. Could I ask you to retry, please? Thanks, jon ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-16 19:18 ` Jonathan Corbet 0 siblings, 0 replies; 30+ messages in thread From: Jonathan Corbet @ 2018-05-16 19:18 UTC (permalink / raw) To: Kim Phillips Cc: Mathieu Poirier, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On Mon, 14 May 2018 12:19:59 -0500 Kim Phillips <kim.phillips@arm.com> wrote: > - Align and show updated ls devices output from the TC2, based on > current driver > > - Provide an example from an ETMv4 based system (Juno) > > - Reflect changes to the way the RAM write pointer is accessed since > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > management entries"). So I was going to apply this, but it's been pretty badly corrupted by your mailer. Could I ask you to retry, please? Thanks, jon -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section 2018-05-16 19:18 ` Jonathan Corbet (?) @ 2018-05-16 20:24 ` Kim Phillips -1 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-16 20:24 UTC (permalink / raw) To: Jonathan Corbet Cc: Mathieu Poirier, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On Wed, 16 May 2018 13:18:23 -0600 Jonathan Corbet <corbet@lwn.net> wrote: > On Mon, 14 May 2018 12:19:59 -0500 > Kim Phillips <kim.phillips@arm.com> wrote: > > > - Align and show updated ls devices output from the TC2, based on > > current driver > > > > - Provide an example from an ETMv4 based system (Juno) > > > > - Reflect changes to the way the RAM write pointer is accessed since > > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > > management entries"). > > So I was going to apply this, but it's been pretty badly corrupted by > your mailer. Could I ask you to retry, please? I had sent a v3 that corrected the issue, in the same thread, here: https://lkml.org/lkml/2018/5/14/1190 Mathieu acked that one. Thanks, Kim ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-16 20:24 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-16 20:24 UTC (permalink / raw) To: linux-arm-kernel On Wed, 16 May 2018 13:18:23 -0600 Jonathan Corbet <corbet@lwn.net> wrote: > On Mon, 14 May 2018 12:19:59 -0500 > Kim Phillips <kim.phillips@arm.com> wrote: > > > - Align and show updated ls devices output from the TC2, based on > > current driver > > > > - Provide an example from an ETMv4 based system (Juno) > > > > - Reflect changes to the way the RAM write pointer is accessed since > > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > > management entries"). > > So I was going to apply this, but it's been pretty badly corrupted by > your mailer. Could I ask you to retry, please? I had sent a v3 that corrected the issue, in the same thread, here: https://lkml.org/lkml/2018/5/14/1190 Mathieu acked that one. Thanks, Kim ^ permalink raw reply [flat|nested] 30+ messages in thread
* Re: [PATCH v2] coresight: documentation: update sysfs section @ 2018-05-16 20:24 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-16 20:24 UTC (permalink / raw) To: Jonathan Corbet Cc: Mathieu Poirier, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel On Wed, 16 May 2018 13:18:23 -0600 Jonathan Corbet <corbet@lwn.net> wrote: > On Mon, 14 May 2018 12:19:59 -0500 > Kim Phillips <kim.phillips@arm.com> wrote: > > > - Align and show updated ls devices output from the TC2, based on > > current driver > > > > - Provide an example from an ETMv4 based system (Juno) > > > > - Reflect changes to the way the RAM write pointer is accessed since > > it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS > > management entries"). > > So I was going to apply this, but it's been pretty badly corrupted by > your mailer. Could I ask you to retry, please? I had sent a v3 that corrected the issue, in the same thread, here: https://lkml.org/lkml/2018/5/14/1190 Mathieu acked that one. Thanks, Kim -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 30+ messages in thread
* [PATCH v4] coresight: documentation: update sysfs section 2018-05-16 20:24 ` Kim Phillips (?) @ 2018-05-31 16:21 ` Kim Phillips -1 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-31 16:21 UTC (permalink / raw) To: Jonathan Corbet Cc: Mathieu Poirier, Randy Dunlap, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Jonathan Corbet <corbet@lwn.net> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v4: v3 + Randy and Mathieu's acked-bys, for Jonathan to apply. v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v4] coresight: documentation: update sysfs section @ 2018-05-31 16:21 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-31 16:21 UTC (permalink / raw) To: linux-arm-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Jonathan Corbet <corbet@lwn.net> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v4: v3 + Randy and Mathieu's acked-bys, for Jonathan to apply. v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root at juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root at juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 ^ permalink raw reply related [flat|nested] 30+ messages in thread
* [PATCH v4] coresight: documentation: update sysfs section @ 2018-05-31 16:21 ` Kim Phillips 0 siblings, 0 replies; 30+ messages in thread From: Kim Phillips @ 2018-05-31 16:21 UTC (permalink / raw) To: Jonathan Corbet Cc: Mathieu Poirier, Randy Dunlap, linux-arm-kernel, open list:DOCUMENTATION, linux-kernel - Align and show updated ls devices output from the TC2, based on current driver - Provide an example from an ETMv4 based system (Juno) - Reflect changes to the way the RAM write pointer is accessed since it got changed in commit 7d83d17795ef ("coresight: tmc: adding sysFS management entries"). Cc: Jonathan Corbet <corbet@lwn.net> Acked-by: Mathieu Poirier <mathieu.poirier@linaro.org> Acked-by: Randy Dunlap <rdunlap@infradead.org> Signed-off-by: Kim Phillips <kim.phillips@arm.com> --- v4: v3 + Randy and Mathieu's acked-bys, for Jonathan to apply. v3: address Randy Dunlap's showns->shown, corrected - and + line merging v2: address Mathieu's comment about clarifying the sinks on the Juno vs. TC2 platforms. Documentation/trace/coresight.txt | 43 +++++++++++++++++++------------ 1 file changed, 26 insertions(+), 17 deletions(-) diff --git a/Documentation/trace/coresight.txt b/Documentation/trace/coresight.txt index 6f0120c3a4f1..15d2a0f1e1b8 100644 --- a/Documentation/trace/coresight.txt +++ b/Documentation/trace/coresight.txt @@ -141,13 +141,25 @@ register the device with the core framework. The unregister function takes a reference to a "struct coresight_device", obtained at registration time. If everything goes well during the registration process the new devices will -show up under /sys/bus/coresight/devices, as showns here for a TC2 platform: +show up under /sys/bus/coresight/devices, as shown here for a TC2 platform: root:~# ls /sys/bus/coresight/devices/ -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:~# +and here for a Juno platform: + +root@juno:~# ls /sys/bus/coresight/devices/ +20010000.etf 20120000.replicator 22040000.etm 230c0000.funnel +20030000.tpiu 20130000.funnel 220c0000.funnel 23140000.etm +20040000.funnel 20140000.etf 22140000.etm 23240000.etm +20070000.etr 20150000.funnel 23040000.etm 23340000.etm +root@juno:~# + +Note that on Juno users can select the ETF, ETR and TPIU as a sink target while +on TC2, the ETB and TPIU can be selected. + The functions take a "struct coresight_device", which looks like this: struct coresight_desc { @@ -193,16 +205,16 @@ the information carried in "THIS_MODULE". How to use the tracer modules ----------------------------- -Before trace collection can start, a coresight sink needs to be identify. +Before trace collection can start, a coresight sink needs to be identified. There is no limit on the amount of sinks (nor sources) that can be enabled at any given moment. As a generic operation, all device pertaining to the sink class will have an "active" entry in sysfs: root:/sys/bus/coresight/devices# ls -replicator 20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm -20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm +20010000.etb 20040000.funnel 2201d000.ptm 2203d000.etm replicator +20030000.tpiu 2201c000.ptm 2203c000.etm 2203e000.etm root:/sys/bus/coresight/devices# ls 20010000.etb -enable_sink status trigger_cntr +enable_sink mgmt power subsystem trigger_cntr uevent root:/sys/bus/coresight/devices# echo 1 > 20010000.etb/enable_sink root:/sys/bus/coresight/devices# cat 20010000.etb/enable_sink 1 @@ -216,16 +228,13 @@ trigger a trace capture: root:/sys/bus/coresight/devices# echo 1 > 2201c000.ptm/enable_source root:/sys/bus/coresight/devices# cat 2201c000.ptm/enable_source 1 -root:/sys/bus/coresight/devices# cat 20010000.etb/status -Depth: 0x2000 -Status: 0x1 -RAM read ptr: 0x0 -RAM wrt ptr: 0x19d3 <----- The write pointer is moving -Trigger cnt: 0x0 -Control: 0x1 -Flush status: 0x0 -Flush ctrl: 0x2001 -root:/sys/bus/coresight/devices# + +Observe the write pointer moving: + +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x1a8 +root:/sys/bus/coresight/devices# cat 20010000.etb/mgmt/rwp +0x19a6 Trace collection is stopped the same way: -- 2.17.0 -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply related [flat|nested] 30+ messages in thread
end of thread, other threads:[~2018-05-31 16:21 UTC | newest] Thread overview: 30+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2018-05-07 22:29 coresight: documentation: update sysfs section Kim Phillips 2018-05-07 22:29 ` Kim Phillips 2018-05-07 22:29 ` Kim Phillips 2018-05-08 15:35 ` Mathieu Poirier 2018-05-08 15:35 ` Mathieu Poirier 2018-05-08 15:35 ` Mathieu Poirier 2018-05-14 17:19 ` [PATCH v2] " Kim Phillips 2018-05-14 17:19 ` Kim Phillips 2018-05-14 17:19 ` Kim Phillips 2018-05-14 18:54 ` Randy Dunlap 2018-05-14 18:54 ` Randy Dunlap 2018-05-14 18:54 ` Randy Dunlap 2018-05-14 19:18 ` [PATCH v3] " Kim Phillips 2018-05-14 19:18 ` Kim Phillips 2018-05-14 19:18 ` Kim Phillips 2018-05-14 21:03 ` Randy Dunlap 2018-05-14 21:03 ` Randy Dunlap 2018-05-14 21:03 ` Randy Dunlap 2018-05-15 16:00 ` Mathieu Poirier 2018-05-15 16:00 ` Mathieu Poirier 2018-05-15 16:00 ` Mathieu Poirier 2018-05-16 19:18 ` [PATCH v2] " Jonathan Corbet 2018-05-16 19:18 ` Jonathan Corbet 2018-05-16 19:18 ` Jonathan Corbet 2018-05-16 20:24 ` Kim Phillips 2018-05-16 20:24 ` Kim Phillips 2018-05-16 20:24 ` Kim Phillips 2018-05-31 16:21 ` [PATCH v4] " Kim Phillips 2018-05-31 16:21 ` Kim Phillips 2018-05-31 16:21 ` Kim Phillips
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.