CoreSight January 2016

coresight@lists.linaro.org

6 participants
7 discussions

by Mathieu Poirier

On 28 January 2016 at 02:18, Eric Long <eric.long(a)linaro.org> wrote: > On 28 January 2016 at 00:02, Mathieu Poirier <mathieu.poirier(a)linaro.org> wrote: >> >> Before going down a CPU will receive notifications, at which point ETM >> configuration registers are saved and tracing interrupted. After a >> CPU went back up the opposite process takes place, i.e registers are >> restored and tracing can resume. The problem with the CPUidle >> approach is that code that bring up and take down CPUs isn't traced. >> >> When dealing with GPDs, the code that switches off a core is always >> the last thing to be executed. The same thing in the opposite >> direction - code that switch on a core is executed first. As such the >> whole path is traced. That is why I favoured that solution but again, >> it is a long way before it can be implemented properly in the kernel. >> At least some people are working on it and I may very well end up >> taking part of that effort but for now, I simply don't have the time. >> >> Whether CPUidle or GPD gets implemented, both will have to deal with >> the intragation of coresight with the perf framework - something that >> will be delicate. >> > > Hi Mathieu, > > Thank you for your detailed explanation. Now I probably understand your > plan. I am very much looking forward to fix the ETM retention issue. Go ahead, it is a very interesting problem to tackle. From hereon let's call the feature "ETM save/restore" - that way people understand what you are referring to. Normally conversations such as this one would be held in a (semi) public forum - the team at Linaro uses "coresight(a)lists.linaro.org". That way people are aware of what is going on and can provide input. Simply subscribe to the list [1] and we will grant you access. > > My original plan was to add retention action into secure code, because > the switch actions of the core power status was be done in secure mode. > The kernel uses psci to comminicate with secure sys. Right, but from a non-secure point of view PSCI is simply an API. All the processing leading to that call happens in the non-secure world. Adding save/restore capabilities in the secure world means that you'd have to synchronise with the CS driver in the non-secure world, and that would be a lot of spaghetti code. > > About the PM runtime and GPD, may be there are some details I need to > understand, and I will spend time to read the PM runtime and GPD code. > If there are any questions I will let you know. And also if there is > anything I can do, please let me know. Thank you. Well, I advise to start with cpu notifiers... The ETMv3 already has support for hotplug notification but that code needs revision. ETMv4 doesn't register any notifier. Mathieu > > Best regards, > Eric [1]. https://lists.linaro.org/mailman/listinfo/coresight

10 years, 1 month

ATCLK on STM

by Chunyan Zhang

Hi Mike, The "Appendix A. CoreSight Port List" in [1] documents that many of CoreSight components have a clock signal called 'ATCLK', but I didn't see the description on STM ATCLK. So is there the 'ATCLK' signal on STM too? At what situations the CoreSight components need ATCLK? Many thanks, Chunyan [1] http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.ddi0314h/Cihejf…

10 years, 1 month

ETM11 and openCSD

by Mathieu Poirier

Hey Mike, A colleague of mine, Linus Walleij, stumbled on a board equipped with an ETM11 and started looking into it. From his point of view it looks simple enough to endeavour providing driver support for it. What kind of trace format does it output? How far are we in openCSD to support traces generated by an ETM11? Thanks, Mathieu

10 years, 1 month

OpenCSD hackfest

by Mathieu Poirier

Tor, Mike and others, A thought dawned on me right after the openCSD meeting on IRC today... >From where I stand things are looking good. Mike has the decoding part pretty much reined in and Tor is moving fast on the perf front. All that's left to do is putting things together, which is what this email is about. Do you guys think it is a good idea to meetup somewhere before Bangkok? Serge is away between the 15th and 19th of February - we could take that opportunity to meet up and work together on openCSD for a week. That would speed up integration and expose everyone to other components of the solution. What are your thoughts on that? I am fully aware that respective company management would have to approve. We'd also need to find a location... Linaro has offices in Cambridge and Boston so that's always a possibility. We could also meet in Blackburn or Houston where ARM and TI are located. Please think about it and talk to your respective management. Chunyan, you are welcome to join us. Best regards, Mathieu

10 years, 1 month

Fwd: My learning summary - STM policy management

by Chunyan Zhang

Good day Mathieu and All, I revised this documentation a little, and re-sending this to you (cc'ed maillist and Mark this time) simply because I want to explain how generic STM deals with master IDs you mentioned in another mail yesterday. To find the answer, you can directly go to 4. - "Allocate one master and a range of channels for stm_source class device:" There are a few concepts / glossaries I need to explain here: i) 'stm_source class device' - is used to write trace data to an stm device once linked, like 'stm_ftrace' you wrote for testing integration of Ftrace with STM before. ii) STM device - means the real hardware device of STM which can be found under /dev/ directory on the target. * STM policy management of master/channel: 1. Policy management source code: driver/hwtrace/stm/policy.c 2. Policy management introduce: (excerpts from Documentation/trace/stm.txt) 1) On the receiving end of this STP stream (the decoder side), trace sources can only be identified by master/channel combination, so in order for the decoder to be able to make sense of the trace that involves multiple trace sources, it needs to be able to map those master/channel pairs to the trace sources that it understands. 2) To solve this mapping problem, stm class provides a policy management mechanism via configfs, that allows defining rules that map string identifiers to ranges of masters and channels. If these rules (policy) are consistent with what decoder expects, it will be able to properly process the trace data. 3. Create policy rules on target: 1) mount -t configfs none /config (the directory 'stp-policy/' will appear under 'config/') 2) Create policy rule for given STM device： mkdir /config/stp-policy/10006000.stm.xxx (‘10006000.stm’ is a STM device name to which this policy applies, this is just an example. ‘xxx’ is an arbitrary string which is separated with device by a dot; but "10006000.stm" must be same with the one which can be found under /dev directory) 3) Create policy rules for a given stm_source class device: mkdir /config/stp-policy/10006000.stm.my_policy/stm_ftrace (‘stm_ftrace’ is a registered device of stm_source class which can be linked with an STM device, and then use this 'stm_ftrace' to write trace data into STM and finally output to the sink buffer. Note that the rule's name must be same with the name of stm_source class device) 4) After created policy rule, there will be two files 'master' and 'channel' under rule's directory, for example: # cat /config/stp-policy/10006000.stm.my_policy/stm_ftrace/masters 0 127 # cat /config/stp-policy/10006000.stm.my_policy/stm_ftrace/channels 0 65535 These values mean the range of master/channels which can be used on the stm_source device whose name is the same with the rule's name (stm_ftrace in this case), the default values come from the configuration [1] of STM device (i.e. 10006000.stm in this case) These master/channel files are configurable and this rule would be applied on the stm_source class device (stm_ftrace) when linking this stm_source class device with any STM device (10006000.stm in this case), for example, if you want to link 'stm_ftrace' with '10006000.stm', you can create the directories '10006000.stm.xxx/stm_ftrace/', and when linking happens, the rule under this directory will be applied on 'stm_ftrace'. 4. Allocate one master and a range of channels for stm_source class device: 1 ) Like mentioned in 3. above, the policy rule which has the same name with the stm_source class device will be applied on this stm_source class device, and then this device can choose its one master and required number of channels from the range which this policy rule defined in "masters" and "channels" files (if there isn't policy rule with the same name, the default configuration of STM device will be applied.) for outputting traces. The number of required channels is configured in the stm_source class device driver. 2) When linking stm_source with STM device happens, the program will poll all masters from either the start master configured in the "masters" file under the policy rule directory if one policy rule was built for this stm_source class device or otherwise struct stm_data::sw_start which is configured in this STM device driver, to see if there are free channels on the current master, and the number of freed continuous channels must be larger than or equal to the quantity of required channels. The first eligible master and channel range will be configured as the output path of this stm_source class device. 5. Allocate master/channels for applictions: 1) Set policy rule which should include 'assigned master', 'first assigned channel', 'the number of required channels' by means of stm_file ioctl interface. 2) If an application program doesn't set policy rule for itself, when this application writing data into STM device, a rule whose name is 'default' will be applied, if the 'default' policy cannot be discovered either, like what I wrote above, the default configuration of STM device will be applied. Regards, Chunyan [1] https://git.linaro.org/people/zhang.chunyan/linux.git/blob/5234c83d13a4eb12…

10 years, 1 month

The result of verifying if STM master need to be managed by software

by Chunyan Zhang

Hi Mathieu, I've finished the verification of STM master stuff on Juno. We indeed don't need to care about which master the trace data should go from software side. The attachments are the result, one is the trace output from Ftrace another is the decoding result with Mike's CS-STM decoding library. FYI: The CPUs and associated STM Mater id on Juno are: CPU Master ID 0 A53 core0 0x44 1 A57 core0 0x40 2 A57 core1 0x41 3 A53 core1 0x45 4 A53 core2 0x46 5 A53 core3 0x47 Regard, Chunyan

10 years, 1 month

Where can I get STM base address

by Chunyan Zhang

Hi All, I'd like to add STM entry for Juno based on Mathieu's patch [1]. But where can I find the STM base address and STM stimulus base address and their ranges. Thanks, Chunyan [1] https://git.linaro.org/people/mathieu.poirier/coresight.git/commit/202357a3…

10 years, 1 month

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

CoreSight January 2016