All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jiri Olsa <jolsa@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@redhat.com>,
	Namhyung Kim <namhyung@kernel.org>,
	Corey Ashford <cjashfor@linux.vnet.ibm.com>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	David Ahern <dsahern@gmail.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH] perf x86: Change SandyBridge and IvyBrige instructions event to be precise
Date: Wed, 20 Feb 2013 12:55:59 -0800	[thread overview]
Message-ID: <m2ppzuyaao.fsf@firstfloor.org> (raw)
In-Reply-To: <1361392794-16552-1-git-send-email-jolsa@redhat.com> (Jiri Olsa's message of "Wed, 20 Feb 2013 21:39:54 +0100")

Jiri Olsa <jolsa@redhat.com> writes:

> Changing the default 'instructions' HW event for SandyBridge and
> IvyBrige to use the available precise 'instructions' event.
>
> The precise event is defined in Intel SDM as:
>
> INST_RETIRED.ALL - Precise instruction retired event with HW to
> reduce effect of PEBS shadow in IP distribution
>
> for both SandyBridge and IvyBrige micro-archs. It allows to use
> precise modifier on 'instructions' event on SandyBridge and
> IvyBrige micro-archs which is not possible now.

Actually it's possible, you just have to use it explicitely.

This will break a lot of profiling setups that assume instructions
count on the fixed counter and use the 4/8 other counters. 
Also it will give very bad results with perf stat, which
you don't want to run with pebs.

Even worse with your change the fixed instruction counter is not
accessible anymore. So pretty much all the standard setups
that collect it in addition to other events and fill all 
the counters would break.

I don't think it should be done by default, but yes explicitely
it's quite useful.

My Haswell patchkit (in the "extended version") exposes
the precise event as "instructions-p" through sysfs.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only

  reply	other threads:[~2013-02-20 20:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20 20:39 [PATCH] perf x86: Change SandyBridge and IvyBrige instructions event to be precise Jiri Olsa
2013-02-20 20:55 ` Andi Kleen [this message]
2013-02-20 21:01   ` Stephane Eranian
2013-02-20 21:29     ` Jiri Olsa
2013-02-20 21:48     ` Andi Kleen
2013-02-20 21:18   ` Jiri Olsa

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=m2ppzuyaao.fsf@firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@redhat.com \
    --cc=cjashfor@linux.vnet.ibm.com \
    --cc=dsahern@gmail.com \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.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.