From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Jonas Jensen <jonas.jensen@gmail.com>
Subject: Re: [PATCH] ARM: disallow ARM_THUMB for ARMv4 builds
Date: Sun, 18 Dec 2016 23:40:53 +0000 [thread overview]
Message-ID: <20161218234053.GQ14217@n2100.armlinux.org.uk> (raw)
In-Reply-To: <CAKv+Gu_KTB+EyQw6-DHEAgswCDvxJTpwH0pJ+ZqB4vz30jrNLA@mail.gmail.com>
On Sun, Dec 18, 2016 at 03:04:24PM +0000, Ard Biesheuvel wrote:
> The only issue I spotted is that the kuser_get_tls routine has only
> two instruction slots for the return sequence, but we can easily work
> around that by moving the TLS hardware instruction around in the
> template (and update the memcpy accordingly in kuser_init()
You can't actually - everything in this page is ABI, and moving
that breaks the ABI.
One thing I'm toying with is splitting out the kuser helpers. That
means we can build it according to the configuration, and select the
appropriate version at run time. Work in progress.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
next prev parent reply other threads:[~2016-12-18 23:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-16 9:14 [PATCH] ARM: disallow ARM_THUMB for ARMv4 builds Arnd Bergmann
2016-12-16 17:20 ` Ard Biesheuvel
2016-12-16 21:51 ` Arnd Bergmann
2016-12-18 11:57 ` Ard Biesheuvel
2016-12-18 14:16 ` Russell King - ARM Linux
2016-12-18 15:04 ` Ard Biesheuvel
2016-12-18 23:40 ` Russell King - ARM Linux [this message]
2016-12-19 4:10 ` Nicolas Pitre
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=20161218234053.GQ14217@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=arnd@arndb.de \
--cc=jonas.jensen@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.pitre@linaro.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).