e81fdcb135d0325e3bc22fae0583555d20aae280 |
|
04-Jan-2017 |
Brendan Jackman <brendan.jackman@arm.com> |
Update ARM Ltd. copyright to 2017
/external/trappy/trappy/stats/Trigger.py
|
05ffbccfb2eaec7ad8a1b6f4c1b8ef2706854089 |
|
26-Feb-2016 |
Javi Merino <javi.merino@arm.com> |
Trigger: narrow the data_frame with the pivot before applying the filter Some complex filters require you to look at previous values of the data. For example, we may want to know when a frequency is no longer used for a given cpu. Trigger(trace, trace.cpu_frequency, pivot="cpu", filters={"frequency": freq_no_longer(max_freq)}, value=-1) freq_no_longer(max_freq) returns True if the previous frequency of this cpu was max_freq and the current is not. The tricky bit is "of this cpu". With the current implementation, all freq_no_longer() sees is the previous value, but it doesn't know to which cpu it corresponds. Filter the data_frame with the pivot (as we are going to end up doing regardless) before applying the filter to avoid exposing the filter to values that are useless to it.
/external/trappy/trappy/stats/Trigger.py
|
f703d77cfc6f8f36051d6e5944370974326afddf |
|
26-Feb-2016 |
Javi Merino <javi.merino@arm.com> |
Trigger: allow filters to be any callable The current test for the filters only checks whether the value of the filter is a function. Actually, we don't care what it is, as long as we can call it. As somebody said in StackOverflow, we're looking for duck-typed objects because we want the ones that quack, not the ones that fit in a duck-sized container. I don't care if you're a rubber duck, if you can quack, I'll apply you to the data frame.
/external/trappy/trappy/stats/Trigger.py
|
adeb9ab49aa913d381ebe1f7000b677c0dd15b4f |
|
26-Feb-2016 |
Javi Merino <javi.merino@arm.com> |
Trigger: simplify looping through filters Use iteritems instead of getting keys and then manually getting the value. Furthermore avoid reassigning operator to value.
/external/trappy/trappy/stats/Trigger.py
|
4ec4aee55dbd4045cfb6a2fe099615a569ce7ff7 |
|
05-Jan-2016 |
Javi Merino <javi.merino@arm.com> |
trappy: update copyright to 2016
/external/trappy/trappy/stats/Trigger.py
|
c26a323210533d4ed3a8b4e62c33744236e3beda |
|
11-Dec-2015 |
Javi Merino <javi.merino@arm.com> |
ftrace: rename Run to FTrace Run is a very generic and inappropriate name for an object that parses the result of ftrace into a form consumable by python. Rename it to FTrace in preparation for its generalization.
/external/trappy/trappy/stats/Trigger.py
|
1ddd9d3bb4633c4fe48ebb8658d6c6449c7fab44 |
|
15-Dec-2015 |
Kapileshwar Singh <kapileshwar.singh@arm.com> |
stats: Fix generation for trigger The trigger.generate function needs to return the value for the valid indices replaced with the trigger value This value replacement was being handled in Aggregator which was accessing a private member from the Trigger class. Removing the _ for making it public was possibly a bad design choice to make pylint happy. Signed-off-by: Kapileshwar Singh <kapileshwar.singh@arm.com>
/external/trappy/trappy/stats/Trigger.py
|
b95a4c5504771224bfe6a4abec759c00d2612a73 |
|
26-Nov-2015 |
Javi Merino <javi.merino@arm.com> |
utils: move listify to a generic trappy.utils file listify() is used in both plotter and stats. Move it out of trappy.plotter.Utils into a generic trappy.utils file as it's not something specific of the plotter.
/external/trappy/trappy/stats/Trigger.py
|
d8fed2c6e783de0b42606177cd062fa265befff2 |
|
09-Sep-2015 |
Kapileshwar Singh <kapileshwar.singh@arm.com> |
doc: Trigger: Use sphinx friendly docstrings Signed-off-by: Kapileshwar Singh <kapileshwar.singh@arm.com>
/external/trappy/trappy/stats/Trigger.py
|
435457c8af9d69383ba45e0bd7da022d967a8dea |
|
10-Aug-2015 |
Javi Merino <javi.merino@arm.com> |
trappy: rename to trappy Change-Id: I7e0e34c9f5565e34629683bb29ab25cf5e737088
/external/trappy/trappy/stats/Trigger.py
|