--- zzzz-none-000/linux-4.4.60/kernel/trace/Kconfig 2017-04-08 07:53:53.000000000 +0000 +++ dragonfly-4020-701/linux-4.4.60/kernel/trace/Kconfig 2018-11-08 13:36:17.000000000 +0000 @@ -86,6 +86,31 @@ Allow the use of ring_buffer_swap_cpu. Adds a very slight overhead to tracing when enabled. +config IPC_LOGGING + bool "Debug Logging for IPC Drivers" + select GENERIC_TRACER + help + This option allows the debug logging for IPC Drivers. + + If in doubt, say no. + +config QCOM_RTB + bool "Register tracing" + help + Add support for logging different events to a small uncached + region. This is designed to aid in debugging reset cases where the + caches may not be flushed before the target resets. + +config QCOM_RTB_SEPARATE_CPUS + bool "Separate entries for each cpu" + depends on QCOM_RTB + depends on SMP + help + Under some circumstances, it may be beneficial to give dedicated space + for each cpu to log accesses. Selecting this option will log each cpu + separately. This will guarantee that the last acesses for each cpu + will be logged but there will be fewer entries per cpu + # All tracer options should select GENERIC_TRACER. For those options that are # enabled by all tracers (context switch and event tracer) they select TRACING. # This allows those options to appear when no other tracer is selected. But the @@ -642,6 +667,19 @@ help Enable tracing events for gpio subsystem +config SRD_TRACE + bool "Record trace events in coherent memory" + depends on FTRACE + default n + help + Normal tracing records the information in cacheable memory. In some + scenarios where the system reboots unexpectedly, the cache is not + flushed and the recorded information is lost. While doing the core + dump analysis, the developer doesn't have the details about the + functions that executed during the final moments before the reboot. + With this option the information is recorded to coherent memory and + the information is not lost even during an unexpected reboot. + endif # FTRACE endif # TRACING_SUPPORT