all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Todd Allen <todd@etallen.com>
To: Vincent Legoll <vincent.legoll@gmail.com>
Cc: 39762@debbugs.gnu.org
Subject: [bug#39762] [PATCH] gnu: cpuid: Update to 20200211.
Date: Mon, 24 Feb 2020 08:12:48 -0700	[thread overview]
Message-ID: <20200224151248.GA27726@toad> (raw)
In-Reply-To: <CAEwRq=qNXOz0Fs=D=PhfBCeyzrzO2Np3ccibYnir8yRcOCdazA@mail.gmail.com>

Vincent,

Yes, often cpuid changes because of new features in the CPUID instruction, or
because of new CPUs determinable by the (synth) and (uarch synth) "leaves".
Sometimes it's because there was a feature I didn't know existed, like 0x2000000
leaves for Itanium.  The ":" change to "=" in a couple cases was deliberate.  It
had been inconsistent before.

Todd

On Sun, Feb 23, 2020 at 11:54:38PM +0100, Vincent Legoll wrote:
> Looks like it is still working in a guix VM running on AMD ryzen 3700X host.
> 
> But there is some output differences between previous version and this one.
> 
> in raw mode (cpuid -r), it outputs one more line per core:
> 
> 0x20000000 0x00: eax=0x00000000 ebx=0x00000000 ecx=0x00000000 edx=0x00000000
> 
> which is probably OK, looks like the change:
> Sun Feb  2 2020 Todd Allen <todd.allen@etallen.com>
>         * cpuid.c: Added leaf walking of the 0x20000000 (Intel Phi) range
>         [...]
> 
> But in normal mode, output changed a lot, some separators changed from ":"
> to "=", a lot of reported values, new things... This will probably break
> any simplistic parsing of that output, if there is anything doing that in
> guix...
> 
> Having a cursory look at the changelog, it looks like this is getting a lot
> more change since the beginning of this year, or something else.
> 
> Maybe Tood Allen can give us a hint...
> 
> Guixers, please advise how to proceed further.
> 
> Thanks--
> Vincent Legoll

> From f15fe227325fe1744ecf58d6bfe513e6c97026fe Mon Sep 17 00:00:00 2001
> From: Vincent Legoll <vincent.legoll@gmail.com>
> Date: Sun, 23 Feb 2020 23:15:33 +0100
> Subject: [PATCH] gnu: cpuid: Update to 20200211. * gnu/packages/linux.scm
>  (cpuid): Update to 20200211.
> 
> ---
>  gnu/packages/linux.scm | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
> index f0fd2fb5df..3fdc716545 100644
> --- a/gnu/packages/linux.scm
> +++ b/gnu/packages/linux.scm
> @@ -5626,14 +5626,14 @@ available in the kernel Linux.")
>  (define-public cpuid
>    (package
>      (name "cpuid")
> -    (version "20200116")
> +    (version "20200211")
>      (source (origin
>                (method url-fetch)
>                (uri (string-append "http://www.etallen.com/cpuid/cpuid-"
>                                    version ".src.tar.gz"))
>                (sha256
>                 (base32
> -                "1gxi4iwy6j366l6bkj1yyxhrk1rxmwfp498gikfxn8xwhij9dn0a"))))
> +                "06sjbqqp80l7nhsp6khglkzdp9qy4vhbvjxbfilznhsmrqiwlw55"))))
>      (build-system gnu-build-system)
>      (arguments
>       '(#:make-flags '("CC=gcc")
> -- 
> 2.25.1
> 

  parent reply	other threads:[~2020-02-24 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-23 22:54 [bug#39762] [PATCH] gnu: cpuid: Update to 20200211 Vincent Legoll
2020-02-23 23:49 ` bug#39762: " Tobias Geerinckx-Rice via Guix-patches via
2020-02-24 15:12 ` Todd Allen [this message]
2020-02-24 19:14   ` [bug#39762] " Vincent Legoll

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=20200224151248.GA27726@toad \
    --to=todd@etallen.com \
    --cc=39762@debbugs.gnu.org \
    --cc=vincent.legoll@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.