[PATCH 3/6] pstore: Add persistent function tracing

Luck, Tony tony.luck at intel.com
Fri Jun 15 22:19:54 UTC 2012

> milli-seconds for recording? This would cripple the kernel. On slow
> machines, incorporating lockdep into function tracing (and other debug
> options) causes the system to live lock. Tracing the timer interrupt
> took so long that by the time it finished, the next timer triggered
> again.

Ah - I think I misunderstood how this works ... I thought the function
trace was taken at some point in the crash/shutdown path.  Now I see
that it is being generated repeatedly as the kernel runs ... with the
idea that if a hang happens, you can see the last call trace that was

Ok then - clearly this is only useful with a ram backend for pstore.

Binary makes sense too - but I'll stick with my comment that a different
kernel must be able to do the decode. Or we need to spell out clearly
that you must have the same, or compatible kernel booted to make any
sense of the saved ftrace record.


More information about the devel mailing list