From: Florian Fainelli <f.fainelli@gmail.com>
To: Al Stone <ahs3@redhat.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: Mark Rutland <mark.rutland@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: Re: [PATCH 3/3] arm64: cpuinfo: display product info in /proc/cpuinfo
Date: Tue, 26 Sep 2017 17:40:20 -0700 [thread overview]
Message-ID: <d186c3fa-5d6f-8865-b824-efcdc7184cb3@gmail.com> (raw)
In-Reply-To: <20170926222324.17409-4-ahs3@redhat.com>
On 09/26/2017 03:23 PM, Al Stone wrote:
> While it is very useful to know what CPU is being used, it is also
> useful to know who made the platform being used. On servers, this
> can point to the right person to contact when a server is having
> trouble.
>
> Go get the product info -- manufacturer, product name and version --
> from DMI (aka SMBIOS) and display it in /proc/cpuinfo. To look more
> like other server platforms, include the CPU type and frequency when
> displaying the product info, too.
>
> Signed-off-by: Al Stone <ahs3@redhat.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will.deacon@arm.com>
> Cc: Suzuki K Poulose <suzuki.poulose@arm.com>
> Cc: Mark Rutland <mark.rutland@arm.com>
> ---
[snip]
> +/* Look up the baseboard info in DMI */
> +static void get_dmi_product_info(void)
> +{
> + if (!dmi_product_info) {
> + dmi_product_info = kcalloc(DMI_MAX_STRLEN,
> + sizeof(char), GFP_KERNEL);
> + if (!dmi_product_info)
> + return;
> + }
> +
> + dmi_walk(find_dmi_product_info, dmi_product_info);
> +}
Don't you need all of these DMI-related functions you defined to be also
enclosed within an #if IS_ENABLED(CONFIG_DMI) otherwise chances are that
we are going to get defined but unused warnings?
> impl = (u8) MIDR_IMPLEMENTOR(midr);
> for (j = 0; hw_implementer[j].id != 0; j++) {
> if (hw_implementer[j].id == impl) {
> @@ -208,7 +341,7 @@ static int c_show(struct seq_file *m, void *v)
> part = (u16) MIDR_PARTNUM(midr);
> for (j = 0; parts[j].id != (-1); j++) {
> if (parts[j].id == part) {
> - seq_printf(m, "%s\n", parts[j].name);
> + seq_printf(m, "%s ", parts[j].name);
> break;
> }
Should this hunk be part of patch 3?
--
Florian
next prev parent reply other threads:[~2017-09-27 0:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 22:23 [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable Al Stone
2017-09-26 22:23 ` [PATCH 1/3] arm64: cpuinfo: add MPIDR value to /proc/cpuinfo Al Stone
2017-09-27 11:33 ` Mark Rutland
2017-09-26 22:23 ` [PATCH 2/3] arm64: cpuinfo: add human readable CPU names " Al Stone
2017-09-27 10:35 ` Robin Murphy
2017-09-27 11:26 ` Mark Rutland
2017-10-13 14:16 ` Timur Tabi
2017-09-26 22:23 ` [PATCH 3/3] arm64: cpuinfo: display product info in /proc/cpuinfo Al Stone
2017-09-27 0:40 ` Florian Fainelli [this message]
2017-09-27 10:42 ` Robin Murphy
2017-09-27 13:39 ` Mark Rutland
2017-09-27 11:36 ` Mark Rutland
2017-10-13 19:27 ` Timur Tabi
2017-09-27 10:34 ` [PATCH 0/3] arm64: cpuinfo: make /proc/cpuinfo more human-readable Mark Rutland
2017-10-09 22:46 ` Al Stone
2017-10-13 13:39 ` Timur Tabi
2017-10-13 14:27 ` Mark Rutland
2017-10-16 23:43 ` Al Stone
2017-10-20 16:10 ` Mark Rutland
2017-10-20 17:24 ` Jon Masters
2017-10-21 0:50 ` Jon Masters
2017-10-20 23:26 ` Al Stone
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=d186c3fa-5d6f-8865-b824-efcdc7184cb3@gmail.com \
--to=f.fainelli@gmail.com \
--cc=ahs3@redhat.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=will.deacon@arm.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
Powered by JetHome