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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 2 May 2019 17:12:56 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Viktor Rosendahl <viktor.rosendahl@...il.com>
Cc:     Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
        Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH v2 4/4] ftrace: Add an option for tracing console
 latencies

On Thu,  2 May 2019 20:37:31 +0200
Viktor Rosendahl <viktor.rosendahl@...il.com> 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 smart enough to pair it. Perhaps return the result of
> > console_stop_critical_timings() and have that passed to
> > console_start_critical_timings(), and only have start do something if
> > stop did something. This way the option only needs to disable the stop
> > part.  
> 
> Something like this?
> 
> I have only compile tested it so far.
> 

Yeah, something like that.

-- Steve