consoleprogram
CPUPRINT.EXE
for
Microsoft®
Windows® NT decodes and prints the
information gathered from the processor’s
CPUID
and XGETBV instructions.
CPUPRINT.LOG
and
CPUPRINT.TXT
show typical outputs for
Intel® Core™
processors;
CPUPRINT.AMD
shows typical output for an
AMD® Athlon™
processor.
Note: CPUPRINT.EXE enumerates the
processor capabilities alias features
IBRS,
STIBP,
IBPB,
L1D_FLUSH
and
SSBD
as well as the presence of the IA32_ARCH_CAPABILITIES
and IA32_FLUSH_CMD model specific registers,
introduced by
AMD
and
Intel
with firmware alias microcode updates to fix the vulnerabilities
CVE-2017-5715
alias Branch Target Injection,
CVE-2017-5753
alias Bounds Check Bypass,
CVE-2017-5754
alias Rogue Data Cache Load,
CVE-2018-3639
alias Speculative Store Bypass,
CVE-2018-3640
alias Rogue System Register Read,
CVE-2018-3693
alias Bounds Check Bypass Store, and
CVE-2018-3615,
CVE-2018-3620
plus
CVE-2018-3646
alias L1 Termination Fault, better known by their
nicknames
Meltdown
,
Spectre
,
Spectre-NG
and
Foreshadow
.
It also enumerates the processor capabilities alias features
PCID,
introduced in first generation Intel Core processors
with Westmere
microarchitecture, and
INVPCID,
introduced in fourth generation Intel Core processors
with Haswell
microarchitecture, both available only in
long mode
, i.e. to 64-bit operating systems, which are
necessary to reduce the performance impact of the fix for
CVE-2017-5754
alias
Meltdown
.
CPUPRINT.NEW
shows the output for an
Intel® Core™ i7-7500U
processor with microcode update applied and all features present;
CPUPRINT.KBL
shows the output for an
Intel® Core™ i5-7400U
processor with microcode update applied and all features present,
running under Microsoft Hyper-V.
Note: when started per double-click, i.e. in its
own console
window, CPUPRINT.EXE waits for a
keypress before it exits and its console
window closes; it
beeps once and flashes the title bar of its console
window
to indicate this wait state.
CPUPRINT.EXE supports multiple specifications of (real
and virtualised) x86 and x64 processors
from several vendors:
CPUPRINT.EXE is a pure Win32
binary executable, written from scratch in
ANSI C,
built without the
MSVCRT
libraries, with the CPUPRINT.EXE is available for the I386
alias x86 and AMD64 alias
x64 processor architectures of
Windows NT.
Note: on the IA64 processor
architecture, the CPUID instruction is supported in
the emulated I386 alias x86 execution
environment only!
Note: CPUPRINT.EXE is neither based
on other outdated tools like
cpuid,
cpuid
or
cpuid
nor related to any of them!
CPUPRINT.EXE
is
digitally signed
using an
X.509
certificate
issued by
WEB.DE TrustCenter E-Mail Certification Authority.
-----BEGIN RSA PUBLIC KEY-----
MIIBCgKCAQEA6ipnm9vAs63w+TM+9UcG1yQ8CRIxMz/tTXry9MCbeHpkiM/qdPaRWlwVTW2j
PhC81xwIPZXgE1FE4DgE1eImb33DG2YfEBY/ARpMaGUnme+85WmExWWc/YMUAaHOMYQ3TQDX
0V/7yuhfa9Uc29ljtQ2AB0MjhXTJvGguvZZTI5A3rcN4+AKwmETdYH+8OQKMU2s+2H9CVfaD
waX0aj9CeibGNooLTgDchzCBIC5J47qHned/3ZqnMDjYCv3Yc1HNgcbM+ZKzPoD8jShb/ptI
wWPo9s00KEs9ti68RsmejqKovAmdLSzFLGARbue2uiqs4piJkxI0LS5+NTTPyZjsSwIDAQAB
-----END RSA PUBLIC KEY-----Note: due to its counter signature alias timestamp the digital signature remains valid past the X.509 certificates expiration date!
Use the X.509 certificate to send S/MIME encrypted mail.
Notes: I dislike
HTML (and
even weirder formats too) in email, I prefer to receive plain text.
I also expect to see your full (real) name as sender, not your
nickname!
Emails in weird formats and without a proper sender name are likely
to be discarded.
I abhor top posts and expect inline quotes in replies.
as iswithout any warranty, neither express nor implied.
cookies.
The service provider for *.homepage.t-online.de, Deutsche Telekom AG,
session cookie.