mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <ak@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	"mingo@elte.hu" <mingo@elte.hu>,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH v2 1/2] perf tools: add event modifier to request exclusive PMU access
Date: Mon, 22 Oct 2012 17:59:25 +0200	[thread overview]
Message-ID: <1350921565.2768.105.camel@twins> (raw)
In-Reply-To: <CABPqkBTeuD==RY9xORYyUhtZm0cXAFw7FEPocMsdCbcqTUS3bg@mail.gmail.com>

On Mon, 2012-10-22 at 17:44 +0200, Stephane Eranian wrote:
> 
> I know the answer, because I know what's going on under the
> hood. But what about the average user? 

I'm still wondering if the avg user really thinks 'instructions' is a
useful metric for other than obtaining ipc measurements.

The avg user wants time domain measurements, like what's the most
expensive function, or most expensive cache-miss etc..



  reply	other threads:[~2012-10-22 16:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-22 13:20 [PATCH v2 0/2] perf: enforce exclusive PMU access for SNB INST_RETIRED:PREC_DIST Stephane Eranian
2012-10-22 13:20 ` [PATCH v2 1/2] perf tools: add event modifier to request exclusive PMU access Stephane Eranian
2012-10-22 13:53   ` Andi Kleen
2012-10-22 14:55     ` Stephane Eranian
2012-10-22 15:39       ` Andi Kleen
2012-10-22 15:44         ` Stephane Eranian
2012-10-22 15:59           ` Peter Zijlstra [this message]
2012-10-22 16:08             ` Stephane Eranian
2012-10-22 17:08               ` Peter Zijlstra
2012-10-22 13:20 ` [PATCH v2 2/2] perf: enforce SNB exclusive access for INST_RETIRED:PREC_DIST Stephane Eranian

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=1350921565.2768.105.camel@twins \
    --to=peterz@infradead.org \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

Powered by JetHome