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  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:   Wed, 05 Aug 2020 22:05:03 -0300
From:   Arnaldo Carvalho de Melo <>
To:     Changbin Du <>
CC:     Jiri Olsa <>,
        Peter Zijlstra <>,
        Ingo Molnar <>,
        Namhyung Kim <>,
        Steven Rostedt <>,
Subject: Re: [PATCH v7 01/18] perf ftrace: select function/function_graph tracer automatically

On August 5, 2020 9:14:48 PM GMT-03:00, Changbin Du <> wrote:
>On Tue, Aug 04, 2020 at 09:51:15AM -0300, Arnaldo Carvalho de Melo
>> Em Sat, Jul 18, 2020 at 02:48:09PM +0800, Changbin Du escreveu:
>> > The '-g/-G' options have already implied function_graph tracer
>should be
>> > used instead of function tracer. So the extra option '--tracer' can
>> > killed.
>> > 
>> > This patch changes the behavior as below:
>> >   - By default, function tracer is used.
>> >   - If '-g' or '-G' option is on, then function_graph tracer is
>> >   - The perf configuration item 'ftrace.tracer' is marked as
>> >   - The option '--tracer' is marked as deprecated.
>> You should try to be more granular, for instance, I think the
>> to change the default is questionable, but could be acceptable.
>> But why deprecate the perf configuration for the default tracer?
>> Say people who already use 'perf ftrace ls' go and use with this
>> and see that it changed the default from the function_graph tracer to
>> the function tracer and disagree with you, they want the default to
>> the function graph tracer, know that there is (or there was) a
>> ftrace.tracer in ~/.prefconfig, and then try that, only to find out
>> it is not possible, frustrating :-\
>> So can we please remove this deprecation of ftrace.tracer so that
>> used to how it was can get that behaviour back?
>Agreed. If no -F or -G is given, we can use the ftrace.tracer as
>default tracer.
>Let me update it. Thanks.

Thanks, I'm general try to be as granular as possible, doing one thing per patch, this way the reviewer can do some preliminary cherry picking and we also improve git bisectability.

- Arnaldo

Sent from my Android device with K-9 Mail. Please excuse my brevity.

Powered by blists - more mailing lists