From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: Andi Kleen <andi@firstfloor.org>,
LKML <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>
Subject: Re: [PATCH] perf x86: Change SandyBridge and IvyBrige instructions event to be precise
Date: Wed, 20 Feb 2013 22:29:44 +0100 [thread overview]
Message-ID: <20130220212943.GB14253@krava.redhat.com> (raw)
In-Reply-To: <CABPqkBTCJF9eF_3Nj9nV=PNqVnrcZhkZ90oJfQ6tpHzFDFgptg@mail.gmail.com>
On Wed, Feb 20, 2013 at 10:01:20PM +0100, Stephane Eranian wrote:
> On Wed, Feb 20, 2013 at 9:55 PM, Andi Kleen <andi@firstfloor.org> wrote:
> > 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.
> >
> There is also the problem that on SNB, PREC_DIST must be
> taken ALONE to be correct. By that, I mean no other counter
> must be active. So I don't think it is a good idea.
>
> Also PREC_DIST is marked as constrained to counter 2 only.
> That in effect, as Andi pointed out, will make the fixed counter
> for instruction_retired, unused because you've set a umask now.
>
> I don't think it buys you much. People read too much into what
> PEBS gives you. I can show you examples where PEBS
> is worse than no PEBS.
well, we sort of advertise we have precise event via precise
modifier and it confused me I was not able to use it on
IvyBridge..
maybe we could export precise alias in sysfs as well which we
could check & use any time there's 'p' modifier specified
not pretty.. meeds more thinking ;-)
thanks,
jirka
next prev parent reply other threads:[~2013-02-20 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 20:39 Jiri Olsa
2013-02-20 20:55 ` Andi Kleen
2013-02-20 21:01 ` Stephane Eranian
2013-02-20 21:29 ` Jiri Olsa [this message]
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=20130220212943.GB14253@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=andi@firstfloor.org \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®