From: Yury Norov <ynorov@caviumnetworks.com>
To: <catalin.marinas@arm.com>, <will.deacon@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <ddaney@caviumnetworks.com>,
Yury Norov <ynorov@caviumnetworks.com>
Subject: [PATCH 0/2] arm64: introduce run-time detection of aarch32 support
Date: Tue, 1 Sep 2015 17:41:10 +0300 [thread overview]
Message-ID: <1441118472-3513-1-git-send-email-ynorov@caviumnetworks.com> (raw)
This is needed to avoid loading aarch32 binaries if COMPAT is enabled, but
aarch32 is not supported by specific platform.
First patch fixes hidden header dependencies in arch/arm64/include/asm/cpufeature.h.
It's not related to the issue, but helps to avoid build failure that happens
if one applies second patch only.
Second patch adds run-time detection of aarch32 support, and rejects kernel to
load such binaries, if not supported.
Tested on ThunderX.
Signed-off-by: Yury Norov <ynorov@caviumnetworks.com>
Yury Norov (2):
arm64: cpufeature.h: resolve hidden header dependencies
arm64: don't load 32-bit binaries if platform has no aarch32_el0
arch/arm64/include/asm/cpufeature.h | 6 ++++++
arch/arm64/include/asm/elf.h | 6 ++++--
arch/arm64/kernel/cpuinfo.c | 9 +++++++++
3 files changed, 19 insertions(+), 2 deletions(-)
--
2.1.4
next reply other threads:[~2015-09-01 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 14:41 Yury Norov [this message]
2015-09-01 14:41 ` [PATCH 1/2] arm64: cpufeature.h: resolve hidden header dependencies Yury Norov
2015-09-01 16:02 ` Mark Rutland
2015-09-01 14:41 ` [PATCH 2/2] arm64: don't load 32-bit binaries if platform has no aarch32_el0 Yury Norov
2015-09-01 16:04 ` Mark Rutland
2015-09-01 17:41 ` Suzuki K. Poulose
2015-09-01 17:44 ` Yury
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=1441118472-3513-1-git-send-email-ynorov@caviumnetworks.com \
--to=ynorov@caviumnetworks.com \
--cc=catalin.marinas@arm.com \
--cc=ddaney@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®