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  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 Apr 2017 12:07:19 +0530
From:   Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:     peterz@...radead.org, mingo@...hat.com,
        alexander.shishkin@...ux.intel.com, alexis.berlemont@...il.com,
        linux-kernel@...r.kernel.org,
        Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
Subject: Re: [PATCH] perf trace: Add usage of --no-syscalls in man page

Hi Arnaldo, Thanks for pulling the patch.

On Thursday 13 April 2017 07:21 PM, Arnaldo Carvalho de Melo wrote:
> Em Thu, Apr 13, 2017 at 11:32:12AM +0530, Ravi Bangoria escreveu:
>> perf trace supports --no-syscalls option but it's not listed in
>> the man page. (Though, I see an example using --no-syscalls in
>> EXAMPLES section.)
> Thanks, applied.
>
> I'm thinking about making --no-syscalls the default when 'trace' is
> hardlinked to 'perf', i.e. 'perf trace'  remains as it is, but if one
> calls 'trace', then --no-syscalls is the default, as after non-syscall
> events got supported I find myself using --no-syscalls way too often,
> what do you think?

+1. Makes sense to me.

I also use 'perf trace' more often for non-syscall events.
So.. if others are okay please do it.

-Ravi

Powered by blists - more mailing lists