Re: [PATCH 3/3] perf_events: add Intel Sandy Bridgeoffcore_response low-level support (v3)

[Peter Zijlstra]

On Mon, 2011-05-23 at 21:29 +0200, Stephane Eranian wrote:
> On Mon, May 23, 2011 at 6:21 PM, Peter Zijlstra <peterz@xxxxxxxxxxxxx> wrote:
> > On Mon, 2011-05-23 at 18:12 +0200, Stephane Eranian wrote:
> >> This patch adds Intel Sandy Bridge offcore_response support by
> >> providing the low-level constraint table for those events.
> >>
> >> On Sandy Bridge, there are two offcore_response events. Each uses
> >> its own dedictated extra register. But those registers are NOT shared
> >> between sibling CPUs when HT is on unlike Nehalem/Westmere. They are
> >> always private to each CPU. But they still need to be controlled within
> >> an event group. All events within an event group must use the same
> >> value for the extra MSR. That's not controlled by the second patch in
> >> this series.
> >>
> >> Furthermore on Sandy Bridge, the offcore_response events have NO
> >> counter constraints contrary to what the official documentation
> >> indicates, so drop the events from the contraint table.
> >
> > You sending this suggests you actually have a SNB machine, do you also
> > happen to know how to use those SNB RSP MSRs? Lin Ming and I were
> > wondering how to fill out the extra-regs for
> > snb_hw_cache_events_jds[C(LL)].
> >
> You first need to describe what you want to measure with those generic
> events. Then, from that, we can try and find a match with the offcore_resp
> bits.

Dude, are you being obtuse on purpose or are you still not getting it?

Exact definitions don't matter, full stop. Pick a random 'exact'
definition of last-level-cache {access(hit+miss),miss} x
{read/write/prefetch} and generate the event that has strongest
correlation to it.

Failing that, explain how to interpret and use those SNB RSP bits and
I'll try, but as it stands the SDM isn't enough for me to even start to
understand how to use that register.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/