From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: linux-kernel@vger.kernel.org, Will Deacon <will.deacon@arm.com>,
Suzuki.Poulose@arm.com
Subject: [PATCH 0/2] arm64: Use static keys for CPU features
Date: Thu, 25 Aug 2016 18:26:30 +0100 [thread overview]
Message-ID: <1472145992-10660-1-git-send-email-catalin.marinas@arm.com> (raw)
This series is aimed to optimise the arm64 cpus_have_cap() functionality
(checking for the presence of certain CPU capabilities/features) to
avoid a bitmap test and use a jump label instead, patched at boot time.
While this series may not provide a clear performance improvement with
the current kernel, it will be more beneficial with new features like
TTBR0 PAN are which are used on hot paths (get_user/put_user, thread
switching).
Catalin Marinas (2):
jump_labels: Allow array initialisers
arm64: Use static keys for CPU features
Documentation/static-keys.txt | 8 ++++++++
arch/arm64/include/asm/cpufeature.h | 14 +++++++++++---
arch/arm64/kernel/cpufeature.c | 3 +++
arch/arm64/kernel/cpuinfo.c | 6 ++++++
include/linux/jump_label.h | 12 ++++++++++++
5 files changed, 40 insertions(+), 3 deletions(-)
next reply other threads:[~2016-08-25 17:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-25 17:26 Catalin Marinas [this message]
2016-08-25 17:26 ` [PATCH 1/2] jump_labels: Allow array initialisers Catalin Marinas
2016-08-30 9:24 ` Catalin Marinas
2016-08-25 17:26 ` [PATCH 2/2] arm64: Use static keys for CPU features Catalin Marinas
2016-08-26 9:22 ` Suzuki K Poulose
2016-09-02 15:52 ` Catalin Marinas
2016-09-02 16:07 ` Suzuki K Poulose
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=1472145992-10660-1-git-send-email-catalin.marinas@arm.com \
--to=catalin.marinas@arm.com \
--cc=Suzuki.Poulose@arm.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;
as well as URLs for NNTP newsgroup(s).