- Status Closed
- Percent Complete
- Task Type Patches
- Category Operating System/Drivers
- Assigned To No-one
- Operating System All players
- Severity Low
- Priority Very Low
- Reported Version Daily build (which?)
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#11161 - Bootchart mode, to measure speed of various tasks during boot
Attached patch adds a bootchart mode (selectable during configure) which uses logf to record various timings during boot: specifically for all the points in boot that involve loading from storage or otherwise may take some time.
I'm looking to put this in svn so that people can compare measurements easily, but the use of the CHART_CALL macro may be considered objectionable (it does make the code a little ahrder to read if you don't know what the macro does). There are only 28 uses of this macro, all in main.c and settings.c, though, so it's not a general pollution of the codebase :)
All opinions and alternative suggestions solicited, as well as comments on useful chart points which have been omitted.
bootchart.diff
(11 KiB)
2010-04-01 16:41
Reason for closing: Fixed
Additional comments about closing: Warning: Undefined array key "typography" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 371 Warning: Undefined array key "camelcase" in /home/rockbox/flyspray/plugins/dokuwiki/inc/parserutils.php on line 407
Committed in r25426, without CHART_CALL,
just explicit string messages.
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task
I'm wondering if you could add a call to logf_function() (or similar) at the beginning of each/some function(s) using the profiling infrastructure, that way you could avoid CHART_CALL() macro's and you'd only have to keep a list of functions/function addresses in memory which should be logged.