public inbox for cygwin-announce@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>
To: "Cygwin Announcements" <cygwin-announce@cygwin.com>
Subject: Updated: cpuid 20211129
Date: Sat, 04 Dec 2021 23:45:29 -0700	[thread overview]
Message-ID: <20211204234529.11946-1-Brian.Inglis@SystematicSW.ab.ca> (raw)

The following package has been upgraded in the Cygwin distribution:

* cpuid		20211129

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 to stay current with Intel and
AMD information and supports other vendors' chips.

See the project home page for more information:

http://etallen.com/cpuid.html

For information about changes since the previous Cygwin release,
see below or /usr/share/doc/cpuid/ChangeLog after installation.


Changes

* From AMD Programmer's Manual, Vol 3, Rev 3.33, Appendix E:
* Added 0x80000008/ebx CPU prefers: IBRS always on.
* Renamed 0x80000008/ebx CPU prefers: STIBP always on.
* Renamed 0x80000008/ebx INVLPGB supports TLB flush guest nested.
* Added 0x8000001f/eax Secure TSC supported, VMSA register protection.
* Added 0x80000021/eax upper address ignore support, SMM_CTL MSR not supported
* Added 0x80000021/ebx, 0x80000022/ebx.
* Correct (uarch synth) phys for Intel Cascade Lake, Cooper Lake to 14nm++.


                 reply	other threads:[~2021-12-05  6:47 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=20211204234529.11946-1-Brian.Inglis@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).