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:   Fri, 14 Aug 2020 08:57:31 -0300
From:   Arnaldo Carvalho de Melo <acme@...nel.org>
To:     Changbin Du <changbin.du@...il.com>
Cc:     Jiri Olsa <jolsa@...hat.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Ingo Molnar <mingo@...hat.com>,
        Namhyung Kim <namhyung@...nel.org>,
        Steven Rostedt <rostedt@...dmis.org>,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v8 05/18] perf ftrace: show trace column header

Em Fri, Aug 14, 2020 at 08:56:55AM -0300, Arnaldo Carvalho de Melo escreveu:
> Em Sat, Aug 08, 2020 at 10:31:28AM +0800, Changbin Du escreveu:
> > This makes perf-ftrace display column header before printing trace.
> > 
> >   $ sudo perf ftrace
> >   # tracer: function
> >   #
> >   # entries-in-buffer/entries-written: 0/0   #P:8
> >   #
> >   #            TASK-PID     CPU#   TIMESTAMP  FUNCTION
> >   #              | |         |       |         |
> >              <...>-9246  [006]  10726.262760: mutex_unlock <-rb_simple_write
> >              <...>-9246  [006]  10726.262764: __fsnotify_parent <-vfs_write
> >              <...>-9246  [006]  10726.262765: fsnotify <-vfs_write
> >              <...>-9246  [006]  10726.262766: __sb_end_write <-vfs_write
> >              <...>-9246  [006]  10726.262767: fpregs_assert_state_consistent <-do_syscall_64
> 
> We have:
> 
>   # perf report -h header
>   
>    Usage: perf report [<options>]
>   
>           --header          Show data header.
>           --header-only     Show only data header.
>   
>   #
> 
> So perhaps we should have those as well, in the 'ftrace' case one would
> perhaps want to use --no-header, for instance, to do some scripting
> parsing just the trace lines.

This as well can be done after I process this series, to make progress.

Applied.

- Arnaldo

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ