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: Thu, 26 May 2011 14:56:04 +0100 [thread overview]
Message-ID: <20110526135604.GA2119@arm.com> (raw)
In-Reply-To: <20110526130104.GA5762@n2100.arm.linux.org.uk>
On Thu, May 26, 2011 at 02:01:04PM +0100, Russell King - ARM Linux wrote:
> On Wed, May 25, 2011 at 03:08:05PM -0700, Vadim Bendebury (??) wrote:
> > On Wed, May 18, 2011 at 3:57 PM, Russell King - ARM Linux <
> > linux at arm.linux.org.uk> wrote:
> > > In which case I think we'll have to talk to kbuild people to get
> > > mkcompile_h modified. Also maybe asking what other architectures
> > > do for this kind of problem may be a good idea - especially before
> > > we start abusing and hacking stuff like the hardware name.
> >
> > So, what would be an equivalent in other architectures to ask about - it
> > seems that the ability to run in Thumb/ARM mode is fairly unique for ARM.
>
> What about 32-bit vs 64-bit x86 ?
Thumb seems different because is is irrelevant to the kernel/user ABI
(or, if it's not irrelevant, we have a bug somewhere...)
Documenting what ISA the kernel was built with is therefore similar to
documenting what optimisation options were used -- i.e., it's interesting
and occasionally useful for humans, but not something software should
normally be querying or care about in any way.
> > Consulting /boot/config file is not reliable: in my own setup I can netboot
> > either thumb or ARM kernel without changing the root file system contents. I
> > agree though that changing the hardware name is not the best way to do this
> > either.
> >
> > I could look into adding 'thumb' to any element of the uname output, or as a
> > watered down version - just add a line to dmesg output?
>
> The thing that I worry about is that userspace will start using this
> information inappropriately. Whether the kernel is built as T2 or ARM
> is really only a matter for the kernel itself (and people debugging the
> kernel), rather than random userspace programs.
Agreed
>
> Maybe a way forward would be to produce a patch for mkcompile_h, post it
> to here, kbuild people and LKML and see what response is forthcoming.
>
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2011-05-26 13:56 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
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 [this message]
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=20110526135604.GA2119@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).