Todo
From Perf Wiki
(Difference between revisions)
Line 19: | Line 19: | ||
* Use the highest precision level available by default, e.g.: cycles:pp | * Use the highest precision level available by default, e.g.: cycles:pp | ||
+ | |||
+ | * Use Kconfig to allow selecting features and build minimal version of perf, e.g. one with just 'record' for use in embedded platforms. |
Revision as of 18:47, 29 January 2013
Perf tools
- Factorize the multidimensional sorting between perf report and annotate (will be used by perf trace)
- Implement a perf cmp (profile comparison between two perf.data) (DONE, its called 'perf diff')
- Implement a perf view (GUI)
- Enhance perf trace:
- Handle the cpu field
- Handle the timestamp
- Use the in-perf ip -> symbol resolving
- Use the in-perf pid -> cmdline resolving
- Implement multidimensional sorting by field name
- The feature tests performed only when a file that needs those tests, or at least only when some .c or .h file will be rebuilt
- Packages needed for the build should be checked before we start building object files, such as bison (bpetkov)
- Forward port the page fault tracepoints and use it in 'trace':
- Use the highest precision level available by default, e.g.: cycles:pp
- Use Kconfig to allow selecting features and build minimal version of perf, e.g. one with just 'record' for use in embedded platforms.