All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Tony Jones <tonyj@suse.de>
Cc: linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@kernel.org>
Subject: Re: restricting counted/sampled events
Date: Thu, 12 Nov 2015 20:08:07 -0300	[thread overview]
Message-ID: <20151112230807.GF7160@kernel.org> (raw)
In-Reply-To: <5644D7DA.7050200@suse.de>

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?

- Arnaldo

  parent reply	other threads:[~2015-11-12 23:08 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 [this message]
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=20151112230807.GF7160@kernel.org \
    --to=acme@kernel.org \
    --cc=jolsa@kernel.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.