From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] ARM: thumb: Have the machine name indicate operation in thumb mode.
Date: Mon, 16 May 2011 15:43:11 +0100 [thread overview]
Message-ID: <20110516144311.GC7715@arm.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1105161008320.14430@xanadu.home>
On Mon, May 16, 2011 at 10:32:16AM -0400, Nicolas Pitre wrote:
> On Mon, 16 May 2011, Dave Martin wrote:
>
> > On Sat, May 14, 2011 at 11:02:32AM +0100, Russell King - ARM Linux wrote:
> > > On Sat, May 14, 2011 at 10:59:14AM +0100, Catalin Marinas wrote:
> > > > On 13 May 2011 20:53, Vadim Bendebury <vbendeb@google.com> wrote:
> > > > > This is a cosmetic change, adding a '_thumb' prefix to the
> > > > > 'Hardware' line in /proc/cpuinfo. Tested as follows:
> > > > >
> > > > > localhost ~ # dmesg | grep thumb
> > > > > [ ? ?0.000000] Machine: kaen_thumb
> > > > > localhost ~ # grep '^Hardware' /proc/cpuinfo
> > > > > Hardware ? ? ? ?: kaen_thumb
> > > > > localhost ~ #
> > > >
> > > > Would this break any script parsing this file?
> > > >
> > > > BTW, why do you need it? You could include the .config into the kernel
> > > > and read it via /proc.
> > >
> > > Whether the kernel is built T2 or ARM doesn't change the userland API
> > > either, so there's no real need for userland to know how the kernel
> > > was built.
> > >
> > > The only thing which is affected by it are kernel modules, but then we
> > > have an established way to sort out incompatible kernel modules already.
> >
> > One corollary to that is that _if_ there's any reason why userland needs to
> > know what instruction set the kernel was built with, then we're probably
> > doing something wrong somewhere...
> >
> > In any case, shoehorning this information into the hardware platform name
> > seems a bit strange since this is really nothing to do with the hardware.
> >
> > Vadim, can you explain why you think this information is needed? If the
> > need is real, perhaps there's a better way to address it.
>
> I think this can be useful to know how the kernel was compiled for bug
> tracking purposes, just like we record the Git commit ID of the checked
> out source tree, the gcc version, the build date, etc. Which pretty
> much indicates that the thumbness of the kernel should probably be
> stored in the kernel banner not the platform name.
That seems a reasonable approach to me.
---Dave
next prev parent reply other threads:[~2011-05-16 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 19:53 [PATCH 1/1] ARM: thumb: Have the machine name indicate operation in thumb mode Vadim Bendebury
2011-05-14 9:59 ` Catalin Marinas
2011-05-14 10:02 ` Russell King - ARM Linux
2011-05-16 12:16 ` Dave Martin
2011-05-16 14:32 ` Nicolas Pitre
2011-05-16 14:43 ` Dave Martin [this message]
2011-05-18 20:59 ` Vadim Bendebury (вб)
2011-05-18 22:27 ` Nicolas Pitre
2011-05-18 22:33 ` Russell King - ARM Linux
2011-05-18 22:49 ` Nicolas Pitre
2011-05-18 22:57 ` Russell King - ARM Linux
[not found] ` <BANLkTinS4XR-QrCsmhStROxkJEy1-PwCTA@mail.gmail.com>
2011-05-26 13:01 ` Russell King - ARM Linux
2011-05-26 13:56 ` Dave Martin
2011-05-26 13:59 ` Russell King - ARM Linux
2011-05-19 8:36 ` Dave Martin
-- strict thread matches above, loose matches on Subject: below --
2011-05-12 0:31 Vadim Bendebury
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=20110516144311.GC7715@arm.com \
--to=dave.martin@linaro.org \
--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;
as well as URLs for NNTP newsgroup(s).