From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: Cygwin Announcements <cygwin-announce@cygwin.com>
Subject: [Updated] cpuid 20200427
Date: Fri, 1 May 2020 01:49:47 -0600 [thread overview]
Message-ID: <c2e1250d-b6f9-b155-62e2-a2d89a99ffa5@SystematicSw.ab.ca> (raw)
The following package has been updated in the Cygwin distribution:
* cpuid 20200427
The program displays detailed information about the CPU(s) gathered from
the CPUID instruction, and also determines the exact model of CPU(s).
Whereas /proc/cpuinfo is like an abstract of the features important to
Linux in a system, cpuid is a standalone utility which writes a paper
expounding on every feature in each CPU's architecture and what it can
do, at about the one line per bit level.
It is updated and released frequently and appears current with Intel and
AMD info and supports other vendors' chips.
Changes
* Added synth decoding for AMD Steppe Eagle/Crowned Eagle (Puma 2014
G-Series), based on instlatx64 sample.
* Added 7/0/edx SERIALIZE & TSXLDTRK bit descriptions.
* Added 0xf/1/eax Counter width & overflow flag.
* Added 0x10/3/ecx per-thread MBA controls flag.
* Added 0x8000001f fields.
* Added AMD 24594 & 40332 docs.
* Corrected field lengths in 14/0 and 14/1 subleafs so that columns line
up.
* Added CC150 (Coffee Lake R0) synth decoding, based on instlatx64
example.
* Added Jasper Lake A0 stepping (from Coreboot*).
* Updated 1/ebx "cpu count" to modern terminology: "maximum addressible
IDs for CPUs in pkg" to avoid user confusion. It was a reliable count
of the number of CPUs for only a split second some time around 2002.
Maybe.
* Updated 4/eax CPU & core count terminology in the same way.
See the project home page for more information:
http://etallen.com/cpuid.html
reply other threads:[~2020-05-01 7:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c2e1250d-b6f9-b155-62e2-a2d89a99ffa5@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--cc=cygwin-announce@cygwin.com \
--cc=cygwin@cygwin.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).