X-Recipient:	archive-cygwin AT delorie DOT com
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org A81D63861970
Authentication-Results:	sourceware.org; dmarc=none (p=none dis=none)
	header.from=SystematicSw.ab.ca
Authentication-Results:	sourceware.org;
	spf=none smtp.mailfrom=brian DOT inglis AT systematicsw DOT ab DOT ca
X-Authority-Analysis:	v=2.3 cv=ePaIcEh1 c=1 sm=1 tr=0
	a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17
	a=IkcTkHD0fZMA:10 a=JZeu4sPTHj9YQVegERsA:9 a=GK4WP9Ryoi6aKYJ2:21
	a=IhsSapby7VoM4kJY:21 a=QEXdDO2ut3YA:10
Subject:	Re: CPU microcode reported wrong in /proc/cpuinfo
To:	cygwin AT cygwin DOT com
References:	<DM6PR09MB404382AB07B3636AFAF09B97A5830 AT DM6PR09MB4043 DOT namprd09 DOT prod DOT outlook DOT com>
	<5f880838-55ad-6f6e-33a6-6a57d7ae9c92 AT SystematicSw DOT ab DOT ca>
From:	Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Autocrypt:	addr=Brian DOT Inglis AT SystematicSw DOT ab DOT ca; prefer-encrypt=mutual;
	keydata=
	mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0
	LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA
	PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW
	AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO
	WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB
	BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5
	/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF
	IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5
	RSyTY8X+AQ==
Organization:	Systematic Software
Message-ID:	<68eea787-9cde-d6ed-499b-61dfc036adff@SystematicSw.ab.ca>
Date:	Thu, 9 Jul 2020 19:27:29 -0600
User-Agent:	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101
	Thunderbird/68.10.0
MIME-Version:	1.0
In-Reply-To:	<5f880838-55ad-6f6e-33a6-6a57d7ae9c92@SystematicSw.ab.ca>
X-CMAE-Envelope:	MS4wfCnde+Mz31Xn0e+aRoNMAknbpx+d546MygqbVgLVsiu06r5Nn0s8QGQBfmupXERKedGW0O0ze4XuLpvAjX6dwbFh7V5ynCd+VXtjV52qRXyICtqW6W3a
	z7oyaZeYJh/zB6BZZefrvC0oSj9qshDsJyQn1TnzU4dDcqZyRwpVNmIjx7IeLHueEIjBZlOoHNOXegjRwk786b+Tq34PJ2HWvKI=
X-Spam-Status:	No, score=-9.3 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS,
	KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, SPF_HELO_NONE, SPF_NONE,
	TXREP autolearn=no autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
Reply-To:	cygwin AT cygwin DOT com
Cc:	"Lavrentiev, Anton \(NIH/NLM/NCBI\) \[C\]" <lavr AT ncbi DOT nlm DOT nih DOT gov>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On 2020-06-10 15:45, Brian Inglis wrote:
> 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!

Managed to get this tested and applied thanks to your help and it has landed in
new Cygwin 3.1.6 so please post your results and any further comments when you
have a chance to upgrade and 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.]
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -