From: Milian Wolff <milian.wolff@kdab.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
mingo@elte.hu, Andi Kleen <ak@linux.intel.com>,
David Ahern <dsahern@gmail.com>
Subject: Re: [RFC] perf script: modify field selection option
Date: Mon, 20 Nov 2017 23:50:27 +0100 [thread overview]
Message-ID: <1733994.9IGknXt0fT@agathebauer> (raw)
In-Reply-To: <CABPqkBQtXcbaimPYf9-QNHQgakJFx7SjGStbDLZ1wKPYYSxzZg@mail.gmail.com>
On Montag, 20. November 2017 21:53:04 CET Stephane Eranian wrote:
> Hi,
>
> I have been using the perf script -F option on the latest perf and I
> find it not very convenient to use. I appreciate the + and - prefix to
> field names to add or suppress them. But most of the time, I want to
> print only one or two fields and I have to guess which ones are there
> by default so I can suppress them. I think there should be a way to
> say: start from no fields. I understand why you have default to
> maintain compatibility with older perf script but I would like a
> syntax to say: remove defaults. For instance:
>
> $ perf script -F --,+ip,+syms .....
>
> Where -- would mean drop all defaults.
>
> Any better suggestions?
Isn't `perf script -F ip,sym` what you want? Note the lack of any '+':
$ perf script -F ip,sym | head -n 5
206aad x86_pmu_enable
380591 ctx_resched
380b46 __perf_event_enable
378716 event_function
Cheers
--
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH&Co KG, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt Experts
next prev parent reply other threads:[~2017-11-20 22:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 20:53 Stephane Eranian
2017-11-20 22:37 ` David Ahern
2017-11-20 22:50 ` Milian Wolff [this message]
2017-11-20 23:21 ` Stephane Eranian
2017-11-21 14:36 ` Arnaldo Carvalho de Melo
2017-11-21 14:35 ` Arnaldo Carvalho de Melo
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=1733994.9IGknXt0fT@agathebauer \
--to=milian.wolff@kdab.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/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
Powered by JetHome