[[File:Lauterbach-eMMC-2-3.png|center|thumb|821x821px|With ftrace, no TRACE32 instrumentation]]
==== Conclusion ====The hardware method based on TRACE32 provides the same log data as recorded by <code>ftrace</code> but with minimal changes to the kernel (a few lines in a file) and a tiny time penalty. It also does not use any additional memory (in terms of RAM and file system storage) and allows for extremely long measurement times.
The following table summarizes the advantages and disadvantages of the two considered solutions: TRACE32 vs <code>ftrace</code>.
{| class="wikitable"
|+Table 3: Pros and cons
!Method
!Pros
!Cons
|-
|TRACE32
|
* Light kernel instrumentation
* No additional memory required
* Long-term analysis (few hours up to over 100 days)
* Can be ported to other OS's / eMMC device drivers.
|
* Hardware-based solution: requires a debug and trace tool + offchip-trace capable processor and target
|-
|<code>ftrace</code>
|
* Software-based solution
|
* Available for Linux kernel only
* Heavy kernel instrumentation
* Time intrusion in eMMC operations
* Kernel program and data size increase
* 10—100 MB of RAM required for ring buffer
* Additional storage device to save the ring buffer
* For each eMMC operation, <code>ftrace</code> saves roughly 876 bytes of log information.
|}
==== Appendix 1: source code example ====
<syntaxhighlight lang="C">
