public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, andi@firstfloor.org,
	zheng.z.yan@intel.com
Subject: Re: [PATCH] perf/x86: fix SNB-EP CBO and PCU uncore PMU filter management
Date: Tue, 21 Aug 2012 12:46:18 +0200	[thread overview]
Message-ID: <1345545978.23018.104.camel@twins> (raw)
In-Reply-To: <20120820162237.GA9295@quad>

On Mon, 2012-08-20 at 18:22 +0200, Stephane Eranian wrote:
>         .constraints            = snbep_uncore_cbox_constraints,
>         .ops                    = &snbep_uncore_msr_ops,
>         .format_group           = &snbep_uncore_cbox_format_group,
> +       .extra_regs             = snbep_uncore_cbo_extra_regs, 

The whole cbo vs cbox thing is a bit unfortunate, I know Intel tends to
forget to type the last letter, but could we be consistent?

Ideally Intel would have called the thing a Cache Coherence Unit or
somesuch to match the Power Control Unit, But seeing its called C-Box, I
don't see the point of saving the 1 character and obfuscate the name.
I've even seen CBO Box used, which is of course completely ridiculous.

  parent reply	other threads:[~2012-08-21 10:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-20 16:22 [PATCH] perf/x86: fix SNB-EP CBO and PCU uncore PMU filter management Stephane Eranian
2012-08-21  8:00 ` Yan, Zheng
2012-08-21 10:46 ` Peter Zijlstra [this message]
2012-08-21 11:45   ` Stephane Eranian
  -- strict thread matches above, loose matches on Subject: below --
2012-10-22  6:02 Yan, Zheng
2012-10-22  6:14 Yan, Zheng

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=1345545978.23018.104.camel@twins \
    --to=peterz@infradead.org \
    --cc=andi@firstfloor.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=zheng.z.yan@intel.com \
    /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