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: failure notice
Date: Sat, 14 Apr 2018 03:51:00 -0000	[thread overview]
Message-ID: <a37c0e51-d617-51a1-ffa0-4fa650268082@SystematicSw.ab.ca> (raw)
In-Reply-To: <CAH8yC8=H9ZcZtJFSOmNFq4WXQN5S6FG_gNwurr7fJ=5-GwYCMg@mail.gmail.com>

On 2018-04-13 21:10, Jeffrey Walton wrote:
>> On Fri, Apr 13, 2018 at 8:36 PM, Jeffrey Walton <noloader@gmail.com> wrote:
>>> 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?
>>
>> The attachment is pp 572-74 from AMD's Programmer's Guide, Volume 3,
>> General-Purpose and System Instructions (December 2017)
>> (https://support.amd.com/TechDocs/24594.pdf). I believe it has the all
>> the necessary information.
>>
>> Are there any objections to using it?
> Any ideas how to get this through? It is a three page PDF extracted from the
> AMD manual. It has the necessary information for the CPUID updates.
Just include the link to Appendix D section 2 from the ToC:
https://support.amd.com/TechDocs/24594.pdf#G14.931059

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

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

  reply	other threads:[~2018-04-14  3:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAH8yC8nrV4i1wOzeBbXDKMJpdfsN-8ZubiN=R7Yow4cBDmG5wQ@mail.gmail.com>
     [not found] ` <5ad17051.cf55650a.73c5d.c3e7SMTPIN_ADDED_MISSING@mx.google.com>
2018-04-14  3:11   ` Jeffrey Walton
2018-04-14  3:51     ` Brian Inglis [this message]
2018-04-14  5:00       ` R0b0t1
2018-04-14  7:27         ` David Stacey
2018-04-14 15:08         ` Brian Inglis
2019-03-02 17:38 Failure notice Andy Perkins
2019-03-02 17:39 ` cygwinautoreply
     [not found] <56619fc2.83c1420a.10961.ffffb37fSMTPIN_ADDED_MISSING@mx.google.com>
2015-12-04 14:20 ` Fwd: failure notice Tom Kacvinsky
2015-12-07 14:01   ` Tom Kacvinsky
     [not found] <5644019f.42dc420a.272e2.5d14SMTPIN_ADDED_MISSING@mx.google.com>
2015-11-12  3:07 ` Mario Roy
     [not found] <CAG=EhJo-oJEFqnmYsuNgewpkq1kpJNnaEbs9AxgKRcfuOZkVjg@mail.gmail.com>
     [not found] ` <545ee223.ea5f460a.2b39.ffff870aSMTPIN_ADDED_MISSING@mx.google.com>
2014-11-09  3:43   ` Theodore Si
     [not found] <CAC8hJujotv3avbCppCX5sOfWjiVJmExfORgtLpKXQ6=eOtgmUQ@mail.gmail.com>
     [not found] ` <4e49a66c.02b7960a.199e.ffffeaaeSMTPIN_ADDED@mx.google.com>
2011-08-15 23:08   ` Gary
  -- strict thread matches above, loose matches on Subject: below --
2009-07-10 14:16 _
2002-09-07 22:48 Fred_Smith
     [not found] <E04CF3F88ACBD5119EFE00508BBB2121015639E4@exch-01.noida.hcltech.com>
2002-01-28 14:39 ` Michael A Chase
1999-07-22 23:56 Teun Burgers
1999-07-26 10:31 ` Chris Faylor
1999-07-31 18:34   ` Chris Faylor
1999-07-31 18:34 ` Teun Burgers

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=a37c0e51-d617-51a1-ffa0-4fa650268082@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).