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] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 7 Aug 2018 11:29:31 -0700
From:   Dave Hansen <dave.hansen@...ux.intel.com>
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     kan.liang@...ux.intel.com, tglx@...utronix.de, mingo@...hat.com,
        len.brown@...el.com, ak@...ux.intel.com,
        linux-kernel@...r.kernel.org, x86@...nel.org
Subject: Re: [PATCH] x86/cpu: Rename Denverton and Gemini Lake

On 08/07/2018 10:48 AM, Peter Zijlstra wrote:
> On Tue, Aug 07, 2018 at 10:35:42AM -0700, Dave Hansen wrote:
>> On 08/07/2018 10:17 AM, kan.liang@...ux.intel.com wrote:
>>> Denverton and Gemini Lake are platform names and should not be used for
>>> Processor Family stuff. The microarchitecture codename should be used.
>> Why?
>>
>> Denverton is the platform.  "Goldmont" is literally the
>> microarchitecture, and you are suggesting moving *to* the
>> microarchitecture name, which contradicts the description.
> All the other (big core) are uarch names. Atom is weird in that it mixes
> uarch with platform names.

Good point.


Feel free to add:  Acked-by: Dave Hansen <dave.hansen@...ux.intel.com>

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ