From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, kan.liang@intel.com
Subject: Re: [PATCH 1/3] perf, x86: Add new cache events table for Haswell
Date: Tue, 10 Feb 2015 18:16:06 +0100 [thread overview]
Message-ID: <20150210171606.GB21418@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20150210171135.GL680@tassilo.jf.intel.com>
On Tue, Feb 10, 2015 at 09:11:35AM -0800, Andi Kleen wrote:
> > Now the other tables create little helpers like:
> >
> > #define HSW_DMND_READ (HSW_DMND_DATA_RD)
> > #define HSW_DMND_WRITE (HSW_DMND_RFO)
> >
> > #define HSW_L3_ACCESS (HSW_ANY_RESPONSE)
> > #define HSW_L3_MISS (HSW_L3_MISS)
> >
> > And compose the tables values using those:
> >
> > HSW_DMND_READ|HSW_L3_ACCESS
> >
> > Please do so here too.
>
> I'm trying to stay with the official documented bit names. No such bit names exist.
> If we make up our own names nobody else can read it anymore.
Well, its a simple matter of looking up the bit definitions; we define
those helpers in terms of the official names after all.
By having the 4 helpers {r,w}x{access,miss} you avoid some repetition
and decrease the room for mistakes.
> > Now; when comparing these value to the SNB for example I note that you
> > include ANY_SNOOP and SUPPLIER_NONE in L3_ACCESS, SNB and other do not,
> > please explain.
>
> You're supposed to set a snoop and supplier qualifier.
> AFAIK SNB should set them too. It may work without them due to some
> quirk.
OK, then we should fix the others. Thanks.
next prev parent reply other threads:[~2015-02-10 17:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 19:17 Andi Kleen
2015-02-09 19:17 ` [PATCH 2/3] perf, x86: Add Broadwell core support Andi Kleen
2015-02-09 19:17 ` [PATCH 3/3] perf, x86: Add INST_RETIRED.ALL workarounds Andi Kleen
2015-02-10 10:34 ` [PATCH 1/3] perf, x86: Add new cache events table for Haswell Peter Zijlstra
2015-02-10 17:11 ` Andi Kleen
2015-02-10 17:16 ` Peter Zijlstra [this message]
2015-02-11 0:40 Andi Kleen
2015-02-12 21:28 ` Peter Zijlstra
2015-02-18 4:58 ` Andi Kleen
2015-02-18 2:18 Andi Kleen
2015-03-23 9:45 ` Ingo Molnar
2015-03-23 13:53 ` Peter Zijlstra
2015-03-23 13:55 ` 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=20150210171606.GB21418@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.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®