From: Jiri Olsa <jolsa@redhat.com>
To: Stephane Eranian <eranian@google.com>
Cc: 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>
Subject: Re: [RFC/PATCH] perf x86: Add off-core event constraints for Sandy/IvyBridge micro architecture
Date: Tue, 29 Jan 2013 16:49:19 +0100 [thread overview]
Message-ID: <20130129154918.GH8339@krava.brq.redhat.com> (raw)
In-Reply-To: <CABPqkBSKGMUAdbqRGUWoaMH1McLDGgZUfHw3P4BAAOLSDYjH8Q@mail.gmail.com>
On Mon, Jan 28, 2013 at 06:49:55PM +0100, Stephane Eranian wrote:
> On Sun, Jan 27, 2013 at 6:33 PM, Jiri Olsa <jolsa@redhat.com> wrote:
> > hi,
> > I was looking at the offcore stuff and it looks like we might
> > be missing some constraints for offcore response events on
> > Sandy/IvyBridge.
> >
> > The table 18.8.5 (Off-core Response Performance Monitoring)
> > in Intel SDM states PMC0 for 0xb7 and PMC3 for 0xbb, but
> > there's no other explanation or related description.
> >
> > I can't say/ack if the counters looks bad or right with or
> > without the patch so far.. so just curious ;-)
> >
> Those are artificial constraints which should not be there.
> Remember that offcore_rsp uses an extra MSR which has
> to be shared by all the counters on the PMU. So a way to
> handle the sharing of that extra MSR is to impose an
> artificial constraint on the event itself. If it can only run
> on one counter, then you get the management of the
> extra MSR for free, i.e., only one event gets it.
>
> In perf_events, we use a more sophisticated dynamic scheme
> which does not use this artificial constraint. We can measure
> the event multiple times and share the extra MSR if possible
> (same value). Why multiple times you might ask? For instance,
> with different priv levels.
>
>
> Hope this helps.
nice, thanks a lot for explanation
jirka
next prev parent reply other threads:[~2013-01-29 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-27 17:33 Jiri Olsa
2013-01-28 17:49 ` Stephane Eranian
2013-01-29 15:49 ` Jiri Olsa [this message]
2013-01-31 11:34 ` Ingo Molnar
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=20130129154918.GH8339@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.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
Powered by JetHome