From: liuj97@gmail.com (Jiang Liu)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Optimize jump label implementation on ARM64
Date: Sun, 13 Oct 2013 22:50:20 +0800 [thread overview]
Message-ID: <1381675827-1610-1-git-send-email-liuj97@gmail.com> (raw)
From: Jiang Liu <jiang.liu@huawei.com>
This patchset tries to optimize arch specfic jump label implementation
for ARM64 by dynamic kernel text patching.
To enable this feature, your toolchain must support "asm goto" extension
and "%c" constraint extesion. Current GCC for AARCH64 doesn't support
"%c", so you need a GCC patch similiar to this:
http://gcc.gnu.org/viewcvs/gcc/trunk/gcc/config/arm/arm.c?view=patch&r1=175293&r2=175565&pathrev=175565
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48637
It has been tested on ARM Fast mode, but not on real hardware yet.
Any comments are welcomed!
V1->V2: address review comments of V1
1) refine comments
2) add a new interface to always synchronize with stop_machine()
when patching code
3) handle endian issue when patching code
Jiang Liu (7):
arm64: introduce basic aarch64 instruction decoding helpers
arm64: introduce interfaces to hotpatch kernel and module code
arm64: move encode_insn_immediate() from module.c to insn.c
arm64: introduce aarch64_insn_gen_{nop|branch_imm}() helper functions
arm64, jump label: detect %c support for ARM64
arm64, jump label: optimize jump label implementation
jump_label: use defined macros instead of hard-coding for better
readability
arch/arm64/Kconfig | 1 +
arch/arm64/include/asm/insn.h | 79 ++++++++++
arch/arm64/include/asm/jump_label.h | 52 +++++++
arch/arm64/kernel/Makefile | 3 +-
arch/arm64/kernel/insn.c | 290 ++++++++++++++++++++++++++++++++++++
arch/arm64/kernel/jump_label.c | 60 ++++++++
arch/arm64/kernel/module.c | 151 ++++---------------
include/linux/jump_label.h | 15 +-
scripts/gcc-goto.sh | 2 +-
9 files changed, 527 insertions(+), 126 deletions(-)
create mode 100644 arch/arm64/include/asm/insn.h
create mode 100644 arch/arm64/include/asm/jump_label.h
create mode 100644 arch/arm64/kernel/insn.c
create mode 100644 arch/arm64/kernel/jump_label.c
--
1.8.1.2
next reply other threads:[~2013-10-13 14:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-13 14:50 Jiang Liu [this message]
2013-10-13 14:50 ` [PATCH v2 1/7] arm64: introduce basic aarch64 instruction decoding helpers Jiang Liu
2013-10-13 14:50 ` [PATCH v2 2/7] arm64: introduce interfaces to hotpatch kernel and module code Jiang Liu
2013-10-13 14:50 ` [PATCH v2 3/7] arm64: move encode_insn_immediate() from module.c to insn.c Jiang Liu
2013-10-13 14:50 ` [PATCH v2 4/7] arm64: introduce aarch64_insn_gen_{nop|branch_imm}() helper functions Jiang Liu
2013-10-14 14:24 ` [PATCH] " Jiang Liu
2013-10-13 14:50 ` [PATCH v2 5/7] arm64, jump label: detect %c support for ARM64 Jiang Liu
2013-10-13 14:50 ` [PATCH v2 6/7] arm64, jump label: optimize jump label implementation Jiang Liu
2013-10-13 14:50 ` [PATCH v2 7/7] jump_label: use defined macros instead of hard-coding for better readability Jiang Liu
2013-10-14 15:19 ` [PATCH v2 0/7] Optimize jump label implementation on ARM64 Will Deacon
2013-10-14 15:24 ` Jiang Liu
2013-10-14 15:40 ` Russell King - ARM Linux
2013-10-14 15:57 ` Jiang Liu
2013-10-14 16:04 ` Russell King - ARM Linux
2013-10-14 16:41 ` Will Deacon
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=1381675827-1610-1-git-send-email-liuj97@gmail.com \
--to=liuj97@gmail.com \
--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).