From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) by sourceware.org (Postfix) with ESMTPS id 919003939C29 for ; Wed, 10 Jun 2020 21:45:31 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 919003939C29 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id j8XKjNz96ng7Kj8XLj6171; Wed, 10 Jun 2020 15:45:31 -0600 X-Authority-Analysis: v=2.3 cv=ecemg4MH c=1 sm=1 tr=0 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=JZeu4sPTHj9YQVegERsA:9 a=GFmO9ZT5g3cCfIh9:21 a=hZ8imxwdKus1qICL:21 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com Subject: Re: CPU microcode reported wrong in /proc/cpuinfo To: cygwin@cygwin.com References: From: Brian Inglis Autocrypt: addr=Brian.Inglis@SystematicSw.ab.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: <5f880838-55ad-6f6e-33a6-6a57d7ae9c92@SystematicSw.ab.ca> Date: Wed, 10 Jun 2020 15:45:30 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfODVB2omah5vy93k86a+M4qUFP1vaYrrpmNEF0S1fSEA3tEy1xE2M39tUtfdTCJb1qjnqwLVEpLiKUnQ3O+FEAXg/v3SLSlFGuQ4M/iYqroGZViB0RUO WVB6yyuL9J6kjF0BCAd2JCImES0Dp4T/n8fDpKy0JfyihFZp+rxMFT35fF+r2o9ISr4OenaEX9cjSg== X-Spam-Status: No, score=-11.9 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, 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@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2020 21:45:32 -0000 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.]