lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CABPqkBR3JP5_PskQ1xvLg_0RzZfH0qyz1sHeqya+Ok4V-sbrXQ@mail.gmail.com>
Date:	Tue, 21 Aug 2012 13:45:48 +0200
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	linux-kernel@...r.kernel.org, mingo@...e.hu, andi@...stfloor.org,
	zheng.z.yan@...el.com
Subject: Re: [PATCH] perf/x86: fix SNB-EP CBO and PCU uncore PMU filter management

On Tue, Aug 21, 2012 at 12:46 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> 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.

Ok, I can resubmit with the word cbox instead.

Still missing is the HA box opcode match/mask support.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ