From: Andi Kleen <ak@linux.intel.com>
To: Stephane Eranian <eranian@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung.kim@lge.com>
Subject: Re: [PATCH] perf, x86: add Intel IvyBridge event scheduling constraints
Date: Wed, 20 Feb 2013 14:08:02 -0800 [thread overview]
Message-ID: <20130220220802.GE23293@tassilo.jf.intel.com> (raw)
In-Reply-To: <CABPqkBS58oMw8Gs7AVN0OMvLuFYH4iXXRHBx3Ep1Mbru=gLVtg@mail.gmail.com>
> > Except for LDM_PENDING the CYCLE_ACTIVITY events have been also added to Sandy Bridge.
> > So it should be also added there.
> >
> As far as I know and I double-checked the documentation I have, there
> is no CYCLE_ACTIVITY
> event on SNB or SNB-EP.
page 19-28 in the Jan 2013 SDM. It was only recently added.
It's only a subset of what you have on Ivy Bridge.
>
> > In fact I think you can still share the table because it would just add some
> > non existent events to Sandy Bridge, which is a noop.
> >
> I don't see the point of this, except saving a few bytes. Isn't it
> better to keep each PMU separate?
Ok, as long as you update the SNB table too.
-Andi
next prev parent reply other threads:[~2013-02-20 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 10:15 [PATCH] perf, x86: add Intel IvyBridge event scheduling constraints Stephane Eranian
2013-02-20 13:58 ` [tip:perf/urgent] perf/x86: Add " tip-bot for Stephane Eranian
2013-02-20 15:43 ` [PATCH] perf, x86: add " Andi Kleen
2013-02-20 19:54 ` Stephane Eranian
2013-02-20 22:08 ` Andi Kleen [this message]
2013-02-21 10:35 ` Stephane Eranian
2013-02-26 5:00 ` yqzhang
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=20130220220802.GE23293@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.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