All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Daniel Gutson <daniel.gutson@tallertechnologies.com>
Cc: Leonardo Boquillon <leonardo.boquillon@tallertechnologies.com>,
	linux-perf-users@vger.kernel.org, eranian@google.com
Subject: Re: Ability for classifying of measurements\
Date: Wed, 04 May 2016 16:50:14 -0700	[thread overview]
Message-ID: <87inytpemh.fsf@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAF5HaEXM+Wko35QCtPqYq3KMai=BOA8kfRcLX60Mad=eYaHetQ@mail.gmail.com> (Daniel Gutson's message of "Wed, 4 May 2016 18:56:02 -0300")

Daniel Gutson <daniel.gutson@tallertechnologies.com> writes:
>>
>> For non self monitoring there were perf patches at some point, but they
>> were rejected because it wasn't clear if a process should be able
>> to opt out of monitoring on its own.
>
> Any link?

Here's an older variant from Jiri https://lwn.net/Articles/568602/

I think there was another newer from Stephane to enable/disable perf
through an prctl, but I can't find it right now.

> (separately, of course): timing is of no help there.
> What I would like to know, is what happened (in terms of performance
> metrics) on each state. I would simply
> call perf_label("state name") on each transition.

Ok. It could be done using the uprobes. But would still need to write
the tools to filter by it.

-Andi

      parent reply	other threads:[~2016-05-04 23:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-19 20:51 Ability for classifying of measurements Leonardo Boquillon
2016-04-20 13:08 ` Andi Kleen
     [not found]   ` <CAF5HaEXOwn0_b=an2RR2FT++ktRXLpAP2WHPE7O=kdVKVRYKVQ@mail.gmail.com>
2016-04-20 16:08     ` Daniel Gutson
2016-04-20 17:47       ` Ability for classifying of measurements\ Andi Kleen
2016-05-04 17:20         ` Daniel Gutson
2016-05-04 17:26           ` Daniel Gutson
2016-05-04 21:41           ` Andi Kleen
2016-05-04 21:56             ` Daniel Gutson
2016-05-04 23:19               ` Vince Weaver
2016-05-04 23:50               ` Andi Kleen [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=87inytpemh.fsf@tassilo.jf.intel.com \
    --to=andi@firstfloor.org \
    --cc=daniel.gutson@tallertechnologies.com \
    --cc=eranian@google.com \
    --cc=leonardo.boquillon@tallertechnologies.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 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.