Bureaucrats, dave_user, Administrators
4,650
edits
Changes
→mmc_request_done
(*) measuring points are the part of functions where the instrumentation is added.
The functions average duration analysis of eMMC accesses highlights the greater weight required by <code>ftrace</code>. The tests were performed under the following conditions. Additional, more detailed charts are provided shown in Appendix 2, which show the following section. They allow to determine that using <code>ftrace </code> also involves a greater dispersion of the runtime durations execution times compared to both the kernel without <code>ftrace </code> and the kernel instrumented only with the code for TRACE32. In particular, the functions <code>mmc_start_request() </code> and <code>mmc_request_done() </code> have a few uS microseconds constant execution time without <code>ftrace</code>, and show a very variable execution time with <code>ftrace</code>, with a maximum time up to 279uS 279 us and 285uS 285 us respectively. TBD
===== Detailed time analysis =====
====== <code>mmc_request_done</code> ======
[[File:Lauterbach-eMMC-2-1.png|center|thumb|821x821px|No ftrace, no TRACE32 instrumentation]]
[[File:Lauterbach-eMMC-2-2.png|center|thumb|819x819px|No ftrace, with TRACE32 instrumentation]]
[[File:Lauterbach-eMMC-2-3.png|center|thumb|821x821px|With ftrace, no TRACE32 instrumentation]]
==== Conclusion ====
</syntaxhighlight>
==== Appendix 2: time details ==== ==== Appendix 3: TRACE32 tools configuration for Arm Cortex-A/R architectures ====
===Device's built-in advanced functionalities===
