From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: David Ahern <dsahern@gmail.com>
Cc: Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, sukadev@linux.vnet.ibm.com, jolsa@redhat.com,
ak@linux.intel.com
Subject: Re: [PATCH] perf mem: add priv level filtering support
Date: Wed, 28 Aug 2013 10:27:03 -0300 [thread overview]
Message-ID: <20130828132703.GD3825@infradead.org> (raw)
In-Reply-To: <521BD4F8.5050504@gmail.com>
Em Mon, Aug 26, 2013 at 04:21:44PM -0600, David Ahern escreveu:
> On 8/26/13 7:11 AM, Stephane Eranian wrote:
> >This patch adds the -u -and -k options to perf to allow
> >filtering of load/store sampling based on priv levels.
> >This may not be supported by all HW platforms.
> >+++ b/tools/perf/Documentation/perf-mem.txt
> >+-k::
> >+ Only sample loads/stores at the user level (default: user + kernel)
> >+-u::
> >+ Only sample loads/stores at the kernel level (default: user + kernel)
> Are the descriptions backwards? In the commit message yuo have -u
> means user level and -k means kernel level; the help message here
> seems backwards.
Looks like it is reversed, yes.
> >+ OPT_BOOLEAN('u', "user-level", &mem.user, "include user-level accesses"),
> >+ OPT_BOOLEAN('k', "kernel-level", &mem.kernel, "include kernel-level accesses"),
And its not clear to say that using -u will _exclude_ kernel samples,
just that it includes user samples, perf top has:
-K, --hide_kernel_symbols hide kernel symbols
-U, --hide_user_symbols hide user symbols
So perhaps we should change both to (and add this to 'report' as well):
-U, --hide_kernel_symbols hide kernel symbols
-K, --hide_user_symbols hide user symbols
To state that:
perf top -K
and
perf top --hide_user_symbols
Are equivalent and asks for 'kernel only' samples, like it seems its the
intent (filtering) of Stephane here, and seems to clarify things?
- Arnaldo
next prev parent reply other threads:[~2013-08-28 13:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 13:11 [PATCH] perf mem: add priv level filtering support Stephane Eranian
2013-08-26 22:21 ` David Ahern
2013-08-28 13:20 ` Stephane Eranian
2013-08-28 13:27 ` Arnaldo Carvalho de Melo [this message]
2013-08-28 13:38 ` Stephane Eranian
2013-08-28 13:53 ` Stephane Eranian
2013-08-28 14:21 ` Arnaldo Carvalho de Melo
2013-09-06 0:15 ` Sukadev Bhattiprolu
2013-09-06 3:41 ` Andi Kleen
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=20130828132703.GD3825@infradead.org \
--to=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 \
--cc=sukadev@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