From: Jisheng Zhang <jszhang@kernel.org>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Andrey Ryabinin <ryabinin.a.a@gmail.com>,
Alexander Potapenko <glider@google.com>,
Andrey Konovalov <andreyknvl@gmail.com>,
Dmitry Vyukov <dvyukov@google.com>,
Alexandre Ghiti <alexandre.ghiti@canonical.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
kasan-dev@googlegroups.com
Subject: [PATCH 0/3] unified way to use static key and optimize pgtable_l4_enabled
Date: Wed, 26 Jan 2022 00:50:33 +0800 [thread overview]
Message-ID: <20220125165036.987-1-jszhang@kernel.org> (raw)
Currently, riscv has several features why may not be supported on all
riscv platforms, for example, FPU, SV48 and so on. To support unified
kernel Image style, we need to check whether the feature is suportted
or not. If the check sits at hot code path, then performance will be
impacted a lot. static key can be used to solve the issue. In the
past FPU support has been converted to use static key mechanism. I
believe we will have similar cases in the future. For example, the
SV48 support can take advantage of static key[1].
patch1 introduces an unified mechanism to use static key for riscv cpu
features.
patch2 converts has_cpu() to use the mechanism.
patch3 uses the mechanism to optimize pgtable_l4_enabled.
[1] http://lists.infradead.org/pipermail/linux-riscv/2021-December/011164.html
Jisheng Zhang (3):
riscv: introduce unified static key mechanism for CPU features
riscv: replace has_fpu() with system_supports_fpu()
riscv: convert pgtable_l4_enabled to static key
arch/riscv/Makefile | 3 +
arch/riscv/include/asm/cpufeature.h | 105 ++++++++++++++++++++++++++++
arch/riscv/include/asm/pgalloc.h | 8 +--
arch/riscv/include/asm/pgtable-64.h | 21 +++---
arch/riscv/include/asm/pgtable.h | 3 +-
arch/riscv/include/asm/switch_to.h | 9 +--
arch/riscv/kernel/cpu.c | 2 +-
arch/riscv/kernel/cpufeature.c | 29 ++++++--
arch/riscv/kernel/process.c | 2 +-
arch/riscv/kernel/signal.c | 4 +-
arch/riscv/mm/init.c | 23 +++---
arch/riscv/mm/kasan_init.c | 6 +-
arch/riscv/tools/Makefile | 22 ++++++
arch/riscv/tools/cpucaps | 6 ++
arch/riscv/tools/gen-cpucaps.awk | 40 +++++++++++
15 files changed, 234 insertions(+), 49 deletions(-)
create mode 100644 arch/riscv/include/asm/cpufeature.h
create mode 100644 arch/riscv/tools/Makefile
create mode 100644 arch/riscv/tools/cpucaps
create mode 100755 arch/riscv/tools/gen-cpucaps.awk
--
2.34.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-01-25 16:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 16:50 Jisheng Zhang [this message]
2022-01-25 16:50 ` [PATCH 1/3] riscv: introduce unified static key mechanism for CPU features Jisheng Zhang
2022-01-25 16:50 ` [PATCH 2/3] riscv: replace has_fpu() with system_supports_fpu() Jisheng Zhang
2022-01-25 16:50 ` [PATCH 3/3] riscv: convert pgtable_l4_enabled to static key Jisheng Zhang
2022-01-25 21:30 ` kernel test robot
2022-01-25 21:30 ` kernel test robot
2022-01-25 21:30 ` kernel test robot
2022-01-26 2:42 ` kernel test robot
2022-01-26 2:42 ` kernel test robot
2022-02-14 23:52 ` [PATCH 0/3] unified way to use static key and optimize pgtable_l4_enabled Palmer Dabbelt
2022-02-15 15:34 ` Jisheng Zhang
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=20220125165036.987-1-jszhang@kernel.org \
--to=jszhang@kernel.org \
--cc=alexandre.ghiti@canonical.com \
--cc=andreyknvl@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ryabinin.a.a@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.