public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ravi Bangoria <ravi.bangoria@linux.vnet.ibm.com>
Cc: peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, alexis.berlemont@gmail.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf trace: Add usage of --no-syscalls in man page
Date: Thu, 13 Apr 2017 10:51:03 -0300	[thread overview]
Message-ID: <20170413135103.GO3275@kernel.org> (raw)
In-Reply-To: <1492063332-5745-1-git-send-email-ravi.bangoria@linux.vnet.ibm.com>

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@linux.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

  reply	other threads:[~2017-04-13 13:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-13  6:02 [PATCH] perf trace: Add usage of --no-syscalls in man page Ravi Bangoria
2017-04-13 13:51 ` Arnaldo Carvalho de Melo [this message]
2017-04-14  6:37   ` Ravi Bangoria
2017-04-17  8:34 ` [tip:perf/core] " tip-bot for Ravi Bangoria

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170413135103.GO3275@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=alexis.berlemont@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ravi.bangoria@linux.vnet.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox