From: Tony Jones <tonyj@suse.de>
To: Jiri Olsa <jolsa@redhat.com>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>,
Stephane Eranian <eranian@google.com>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: restricting counted/sampled events
Date: Mon, 16 Nov 2015 08:26:02 -0800 [thread overview]
Message-ID: <564A039A.5050105@suse.de> (raw)
In-Reply-To: <20151116085952.GD5769@krava.brq.redhat.com>
On 11/16/2015 12:59 AM, Jiri Olsa wrote:
> On Thu, Nov 12, 2015 at 08:08:07PM -0300, Arnaldo Carvalho de Melo wrote:
>> Em Thu, Nov 12, 2015 at 10:18:02AM -0800, Tony Jones escreveu:
>>
>>> I don't believe there is current support to do this, but maybe I'm
>>> overlooking something?
>>
>>> 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?
>>
>> Something like this:
>>
>> https://lkml.org/lkml/2013/9/25/227
>>
>> Jiri?
>
> yep.. sounds like toggling ;-) this code was put aside ATM
>
> not sure it'll be ressurected soon, but I remember Stephane asked
> me about that some time ago (CC-ed), maybe he has more info
>
> jirka
If noone is currently working on it, I'd be interested in taking it over.
Tony
prev parent reply other threads:[~2015-11-16 16:33 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
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 [this message]
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=564A039A.5050105@suse.de \
--to=tonyj@suse.de \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@kernel.org \
--cc=jolsa@redhat.com \
--cc=linux-perf-users@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).