From: Andi Kleen <andi@firstfloor.org>
To: Tony Jones <tonyj@suse.de>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: restricting counted/sampled events
Date: Thu, 12 Nov 2015 14:58:45 -0800 [thread overview]
Message-ID: <87fv0a3jve.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <5644D7DA.7050200@suse.de> (Tony Jones's message of "Thu, 12 Nov 2015 10:18:02 -0800")
Tony Jones <tonyj@suse.de> writes:
> I don't believe there is current support to do this, but maybe I'm overlooking something?
It may be possible in systemtap, but not in the builtin tracers yes.
>
> I'd like to be able to restrict the pmu (or filter results) to report counting/sampling between two arbitrary code points, such as a tracepoint or kprobe.
>
> I believe it will require core perf changes and was curious on peoples thoughts?
I'm not sure about messing with sampling (you can always filter that
later).
But able to collect PMU counter values are kprobes/tracepoints would be
fairly useful yes. It shouldn't be that difficult to do.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2015-11-12 22:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 18:18 restricting counted/sampled events Tony Jones
2015-11-12 22:58 ` Andi Kleen [this message]
2015-11-12 23:08 ` Arnaldo Carvalho de Melo
2015-11-13 0:05 ` Tony Jones
2015-11-16 8:59 ` Jiri Olsa
2015-11-16 16:26 ` Tony Jones
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=87fv0a3jve.fsf@tassilo.jf.intel.com \
--to=andi@firstfloor.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=tonyj@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.