From: Chen Zhongjin <chenzhongjin@huawei.com>
To: <linux-kernel@vger.kernel.org>, <linux-crypto@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <herbert@gondor.apana.org.au>, <davem@davemloft.net>,
<catalin.marinas@arm.com>, <will@kernel.org>,
<broonie@kernel.org>, <ardb@kernel.org>, <maz@kernel.org>,
<mark.rutland@arm.com>, <anshuman.khandual@arm.com>,
<chenzhongjin@huawei.com>
Subject: [PATCH -next 0/3] arm64: Mark constants in .S files as data
Date: Thu, 22 Sep 2022 21:04:49 +0800 [thread overview]
Message-ID: <20220922130452.233323-1-chenzhongjin@huawei.com> (raw)
There are some constant numbers insdide .S files which is mixed with
text sections. When tools are reading the ELF files they cannot
distinguish these constants out of normal instructions.
Mark these constants as data symbols by wrapping then with SYM_DATA
macro.
Chen Zhongjin (3):
arm64: efi-header: Mark efi header as data
arm64: head: Mark constants as data
arm64: crypto: Mark constant as data
arch/arm64/crypto/aes-neonbs-core.S | 14 +++++++-------
arch/arm64/crypto/poly1305-armv8.pl | 4 ++++
arch/arm64/crypto/polyval-ce-core.S | 7 +++----
arch/arm64/crypto/sha512-armv8.pl | 24 ++++++++++++++----------
arch/arm64/kernel/efi-header.S | 2 ++
arch/arm64/kernel/head.S | 6 ++++--
6 files changed, 34 insertions(+), 23 deletions(-)
--
2.17.1
next reply other threads:[~2022-09-22 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 13:04 Chen Zhongjin [this message]
2022-09-22 13:04 ` [PATCH -next 1/3] arm64: efi-header: Mark efi header " Chen Zhongjin
2022-09-22 13:13 ` Ard Biesheuvel
2022-09-22 14:25 ` Chen Zhongjin
2022-09-22 13:04 ` [PATCH -next 2/3] arm64: head: Mark constants " Chen Zhongjin
2022-09-22 13:17 ` Ard Biesheuvel
2022-09-22 13:04 ` [PATCH -next 3/3] arm64: crypto: Mark constant " Chen Zhongjin
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=20220922130452.233323-1-chenzhongjin@huawei.com \
--to=chenzhongjin@huawei.com \
--cc=anshuman.khandual@arm.com \
--cc=ardb@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=will@kernel.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
all inboxes | Powered by JetHome®