Re: [PATCH v2 4/4] ftrace: Add an option for tracing console latencies

2019-05-02 Thread Steven Rostedt
On Thu, 2 May 2019 20:37:31 +0200 Viktor Rosendahl wrote: > > Instead of this being turned into a nop, don't have a kconfig option > > but instead have this call into the trace_irqsoff.c code, and depending > > on what the options are, it should stop it. Of course, this would need > > to be smar

Re: [PATCH v2 4/4] ftrace: Add an option for tracing console latencies

2019-05-02 Thread Viktor Rosendahl
> Instead of this being turned into a nop, don't have a kconfig option > but instead have this call into the trace_irqsoff.c code, and depending > on what the options are, it should stop it. Of course, this would need > to be smart enough to pair it. Perhaps return the result of > console_stop_crit

Re: [PATCH v2 4/4] ftrace: Add an option for tracing console latencies

2019-05-01 Thread Steven Rostedt
On Wed, 1 May 2019 22:36:50 +0200 Viktor Rosendahl wrote: > This new option CONFIG_TRACE_CONSOLE_LATENCY will enable the latency > tracers to trace the console latencies. Previously this has always been > implicitely disabled. I guess this is because they are considered > to be well known and un

[PATCH v2 4/4] ftrace: Add an option for tracing console latencies

2019-05-01 Thread Viktor Rosendahl
This new option CONFIG_TRACE_CONSOLE_LATENCY will enable the latency tracers to trace the console latencies. Previously this has always been implicitely disabled. I guess this is because they are considered to be well known and unavoidable. However, for some organizations it may nevertheless be de