linux-kernel - Re: [PATCH x86 for review III] [17/29] x86: Add new CPUID bits for AMD Family 10 CPUs in /proc/cpuinfo

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]

Message-ID: <45D0EC39.8030608@redhat.com>
Date:	Mon, 12 Feb 2007 17:37:45 -0500
From:	Chuck Ebbert <cebbert@...hat.com>
To:	Andi Kleen <andi@...stfloor.org>
CC:	patches@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH x86 for review III] [17/29] x86: Add new CPUID bits for
 AMD Family 10 CPUs in /proc/cpuinfo

Andi Kleen wrote:

>> Since we seem to have become the place where all these are collected,
>> shouldn't we document what they mean?
> 
> This is not a data sheet and the CPU vendors have fine tech writers
> working on this already.
> 
> Also I don't really want to encourage people to hack this without
> at least taking a basic look at the documentation first.
> 
>> I've got some this machine that 
>> I'd like to know more about:
>>
>> dts ss ds_cpl est tm2 ssse3 xtpr
> 
> All documented in Intel documentation. But it's all relatively boring stuff
> 
> dts = debug trace store
> ss = self snoop
> ds_cpl = cpl qualified debug store
> est = enhanced speedstep
> tm2 = thermal monitor 2
> ssse3 = more sse3 instructions
> xtpr = tpr register chipset update control msr
> 

That's exactly what I was asking for.  Our abbreviations are too cryptic
to let someone go look up the meanings without a lot of trouble.

A one-liner for each in the comments would be just enough.

-
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/