From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: CPU microcode reported wrong in /proc/cpuinfo
Date: Thu, 16 Jul 2020 14:13:49 -0600 [thread overview]
Message-ID: <839d4123-c77e-e53e-9c19-cfcc38209c0a@SystematicSw.ab.ca> (raw)
In-Reply-To: <04c2c0ea-1e27-508b-c054-a5ad8e1da240@SystematicSw.ab.ca>
On 2020-07-16 13:46, Brian Inglis wrote:
> On 2020-07-16 08:56, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
> It may be possible that Windows executes a CPUID instruction, and then reads MSR
Intel states CPUID of leaf EAX = 1, so not reading that leaf may not update MSR.
> 8BH IA32_BIOS_SIGN_ID to get the current value, without first preloading the MSR
> with zero, and rather than interpreting the zero result as unchanged, just
> reports that value.
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in IEC units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-07-16 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 20:23 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis
2020-07-10 1:27 ` Brian Inglis
2020-07-16 14:56 ` Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-07-16 19:46 ` Brian Inglis
2020-07-16 20:13 ` Brian Inglis [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-07-16 20:41 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-07-16 20:36 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 15:34 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-10 21:45 ` Brian Inglis
2020-05-31 15:07 Lavrentiev, Anton (NIH/NLM/NCBI) [C]
2020-06-02 20:11 ` Brian Inglis
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=839d4123-c77e-e53e-9c19-cfcc38209c0a@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).