From: Huang Shijie <shijie@os.amperecomputing.com>
To: Jeremy Linton <jeremy.linton@arm.com>
Cc: Karel Zak <kzak@redhat.com>,
util-linux@vger.kernel.org, patches@amperecomputing.com,
zwang@amperecomputing.com, mas@amperecomputing.com,
ilkka@os.amperecomputing.com,
Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>,
jbastian@redhat.com
Subject: Re: [PATCH] lscpu: get the processor information by DMI
Date: Tue, 15 Jun 2021 09:23:01 +0000 [thread overview]
Message-ID: <YMhxdX+e2Kkx/++w@hsj> (raw)
In-Reply-To: <ec45d3f7-6c6f-08c7-3d0d-9f38723c1d97@arm.com>
On Mon, Jun 14, 2021 at 03:00:16PM -0500, Jeremy Linton wrote:
Hi Jeremy,
> > > After this patch, we can get the lscpu output
> > > in Ampere Altra platform:
> > > ---------------------------------------------
> > > Architecture: aarch64
> > > CPU op-mode(s): 32-bit, 64-bit
> > > Byte Order: Little Endian
> > > CPU(s): 160
> > > On-line CPU(s) list: 0-159
> > > Vendor ID: ARM
> > > Model name: Ampere(R) Altra(R) Processor Q00-00 CPU @ 3.0GHz
>
> >
> > Should be
> >
> > Model name: Neoverse-N1
> > BIOS Model name: Ampere(R) Altra(R) Processor Q00-00 CPU @ 3.0GHz
>
> Right, another example :
>
>
> Vendor ID: ARM
> BIOS Vendor ID: Broadcom
> Model name: Cortex-A72
> BIOS Model name: BCM2711 (ARM Cortex-A72)
>
>
> Which is helpful when comparing with various other utilities, like gcc,
> which take cortex-a72 as -mtune parameters.
okay. thanks. I will change it in next version.
Thanks
Huang Shijie
next prev parent reply other threads:[~2021-06-15 2:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 9:48 [PATCH] lscpu: get the processor information by DMI Huang Shijie
2021-06-14 10:41 ` Karel Zak
2021-06-14 20:00 ` Jeremy Linton
2021-06-15 9:23 ` Huang Shijie [this message]
2021-06-15 9:20 ` Huang Shijie
2021-06-15 8:48 ` Karel Zak
2021-06-15 9:13 ` Karel Zak
2021-06-15 9:14 ` Huang Shijie
2021-06-15 9:13 ` Huang Shijie
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=YMhxdX+e2Kkx/++w@hsj \
--to=shijie@os.amperecomputing.com \
--cc=ilkka@os.amperecomputing.com \
--cc=jbastian@redhat.com \
--cc=jeremy.linton@arm.com \
--cc=kzak@redhat.com \
--cc=m.mizuma@jp.fujitsu.com \
--cc=mas@amperecomputing.com \
--cc=patches@amperecomputing.com \
--cc=util-linux@vger.kernel.org \
--cc=zwang@amperecomputing.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 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.