On 03.12.2016 12:52, Paul Menzel via coreboot wrote: > After rebuilding the utility `cbmem`, the relevant output looks like > below. > > ``` > 60:device initialization 457,880 (9,886) > 120:starting timer init 472,001 (14,121) > 121:finished timer init 472,008 (6) > 70:device setup done 472,751 (742) > ``` > > Would that be acceptable to have nested entries? The down side is, the > time from *device initialization* to *device setup done* has to be > calculated manually now.
It's actually simple to make `cbmem` aware of the nesting, if you'd store the level of the nesting for each timestamp. All that `cbmem` would then have to do is, store the last timestamp of each level in an array, and everytime it encounters a decrease in level, output a third number, that is the difference of the current to the last timestamp of its level. Nico -- coreboot mailing list: [email protected] https://www.coreboot.org/mailman/listinfo/coreboot
