This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Incorrect /proc/cpuinfo for AMD A6-9220
- From: Jeffrey Walton <noloader at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 13 Apr 2018 20:36:56 -0400
- Subject: Re: Incorrect /proc/cpuinfo for AMD A6-9220
- References: <CAH8yC8k4U-DO0n8r_K=93jPkXCQ=qH8ZMv8CasmkN5=K3UOMLA@mail.gmail.com> <20180413115120.GA27440@calimero.vinschen.de>
- Reply-to: noloader at gmail dot com
On Fri, Apr 13, 2018 at 7:51 AM, Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> On Apr 12 23:01, Jeffrey Walton wrote:
>> Hi Everyone,
>>
>> I'm working on an AMD A6-9220 and seeing unusual results from
>> /proc/cpuinfo. I think this may be an issue with the latest Cygwin. It
>> may be present in earlier versions, too.
>>
>> Russinovich's coreinfo is shown below
>> (https://docs.microsoft.com/en-us/sysinternals/downloads/coreinfo).
>> Notice /proc/cpuinfo is missing aesni, pclmul, rdrand, SSE4.1, SSE4.2,
>> AVX, etc.
>
> Note that, in theory, cpuinfo has to be extended for each new CPU
> generation. That's a lot of work for marginal gain (Cygwin's not a real
> kernel) so I'm doing this only very seldomly.
>
> Patches welcome, of course!
Thanks Corinna. I think I found the file of interest at fhandler_proc.cc.
Whitespace is a bit off. It is a mix of tabs and space:
if (features1 & (1 << 0))
print (" fpu");
if (features1 & (1 << 1))
print (" vme");
Should I perform a whitespace check-in before things begin? Or can you
knock it out?
Jeff
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple