public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: CPU microcode reported wrong in /proc/cpuinfo
Date: Wed, 10 Jun 2020 15:45:30 -0600	[thread overview]
Message-ID: <5f880838-55ad-6f6e-33a6-6a57d7ae9c92@SystematicSw.ab.ca> (raw)
In-Reply-To: <DM6PR09MB404382AB07B3636AFAF09B97A5830@DM6PR09MB4043.namprd09.prod.outlook.com>

On 2020-06-10 14:23, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via Cygwin wrote:
>> I'll have to recheck how Linux handles these
> 
> JFYI I was in correspondence with the cpuid utility team lately, and they told me that Linux uses vendor-specific MSRs to pull that info out:
> 
>> Check out:
>>
>>    MSR_IA32_UCODE_REV
>>    MSR_AMD64_PATCH_LEVEL
>>
>> Both reference MSR 0x8b.

As does MS, as I also tracked down some older MS Windows microcode registry
values used, whose names also appear to be based on the earlier MSR names.
Using MSRs are not an option, as MS Windows appears to provide no documented
access to those register values, and they are only accessible from kernel level
drivers, which are not available for latest MS Windows (i.e. I don't trust
offered drivers that claim to provide MSR access!)

I have applied a patch for this, and rebuilt cygwin, but are having problems
testing with the new dll (as are some others), so need some time to figure out
what are the minimum synced pieces now required to be able to test!

-- 
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.]

  reply	other threads:[~2020-06-10 21:45 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 [this message]
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
  -- 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=5f880838-55ad-6f6e-33a6-6a57d7ae9c92@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).