[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170413135103.GO3275@kernel.org>
Date: Thu, 13 Apr 2017 10:51:03 -0300
From: Arnaldo Carvalho de Melo <acme@...nel.org>
To: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
Cc: peterz@...radead.org, mingo@...hat.com,
alexander.shishkin@...ux.intel.com, alexis.berlemont@...il.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] perf trace: Add usage of --no-syscalls in man page
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?
Or perhaps have a 'perf strace' to try to have as much in common with
'strace' in terms of default behaviour, options, etc?
- Arnaldo
> Signed-off-by: Ravi Bangoria <ravi.bangoria@...ux.vnet.ibm.com>
> ---
> tools/perf/Documentation/perf-trace.txt | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/tools/perf/Documentation/perf-trace.txt b/tools/perf/Documentation/perf-trace.txt
> index afd7286..c1e3288 100644
> --- a/tools/perf/Documentation/perf-trace.txt
> +++ b/tools/perf/Documentation/perf-trace.txt
> @@ -123,7 +123,8 @@ the thread executes on the designated CPUs. Default is to monitor all CPUs.
> major or all pagefaults. Default value is maj.
>
> --syscalls::
> - Trace system calls. This options is enabled by default.
> + Trace system calls. This options is enabled by default, disable with
> + --no-syscalls.
>
> --call-graph [mode,type,min[,limit],order[,key][,branch]]::
> Setup and enable call-graph (stack chain/backtrace) recording.
> --
> 2.1.4
Powered by blists - more mailing lists