From: mark.rutland@arm.com (Mark Rutland)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] arm64: clean up /proc/cpuinfo
Date: Mon, 30 Jun 2014 10:13:52 +0100 [thread overview]
Message-ID: <20140630091352.GP7262@leverpostej> (raw)
In-Reply-To: <20140628010440.9839.9366.stgit@bhelgaas-glaptop.roam.corp.google.com>
Hi Bjorn,
On Sat, Jun 28, 2014 at 02:11:58AM +0100, Bjorn Helgaas wrote:
> On arm64, /proc/cpuinfo currently looks like:
>
> Processor : AArch64 Processor rev 0 (aarch64)
> processor : 0
> processor : 1
> ...
> Features : ...
>
> Compared to most other architectures (including arm), this has an extra
> "Processor" header, and the "Features" and other bits only appear once,
> so there's no way to have per-CPU features, variants, etc.
>
> These patches make arm64 more consistent with the other architectures
> by removing the extra header and printing the CPU ID information for
> each CPU.
This looks very much like the series I've been working on [1,2,3], that
reports the MIDR information and performs some additional sanity
checking (expecting CPUs to have identical hwcap features).
Did you need this for any reason it particular, or was this just a clean
up?
Does my series look OK to you?
Cheers,
Mark.
[1] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-May/255389.html
[2] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/264387.html
[3] http://lists.infradead.org/pipermail/linux-arm-kernel/2014-June/266973.html
next prev parent reply other threads:[~2014-06-30 9:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 1:11 [PATCH 0/2] arm64: clean up /proc/cpuinfo Bjorn Helgaas
2014-06-28 1:12 ` [PATCH 1/2] arm64: add MIDR to per-CPU information Bjorn Helgaas
2014-06-28 1:12 ` [PATCH 2/2] arm64: kernel: update cpuinfo to print all online CPUs features Bjorn Helgaas
2014-06-29 8:51 ` [PATCH 0/2] arm64: clean up /proc/cpuinfo Catalin Marinas
2014-06-30 9:13 ` Mark Rutland [this message]
2014-06-30 15:19 ` Bjorn Helgaas
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=20140630091352.GP7262@leverpostej \
--to=mark.rutland@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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