From: Jisheng Zhang <jszhang3@mail.ustc.edu.cn>
To: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Masahiro Yamada <masahiroy@kernel.org>,
Michal Marek <michal.lkml@markovi.net>,
Nick Desaulniers <ndesaulniers@google.com>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-kbuild@vger.kernel.org
Subject: [PATCH 0/2] riscv: switch to relative extable
Date: Sun, 17 Oct 2021 00:04:08 +0800 [thread overview]
Message-ID: <20211017000408.4ae9ecd6@xhacker> (raw)
From: Jisheng Zhang <jszhang@kernel.org>
Similar as other architectures such as arm64, x86 and so on, use
offsets relative to the exception table entry values rather than
absolute addresses for both the exception locationand the fixup.
patch1 consolidates the __ex_table construction, it's a great code
clean up even w/o the 2nd patch.
patch2 does the real job.
Jisheng Zhang (2):
riscv: consolidate __ex_table construction
riscv: switch to relative exception tables
arch/riscv/include/asm/Kbuild | 1 -
arch/riscv/include/asm/extable.h | 25 ++++++++++++++++++++
arch/riscv/include/asm/futex.h | 12 +++-------
arch/riscv/include/asm/uaccess.h | 40 +++++++++++---------------------
arch/riscv/lib/uaccess.S | 4 ++--
arch/riscv/mm/extable.c | 2 +-
scripts/mod/modpost.c | 27 +++++++++++++++++++++
scripts/sorttable.c | 2 +-
8 files changed, 73 insertions(+), 40 deletions(-)
create mode 100644 arch/riscv/include/asm/extable.h
--
2.33.0
next reply other threads:[~2021-10-16 16:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 16:04 Jisheng Zhang [this message]
2021-10-16 16:04 ` [PATCH 1/2] riscv: consolidate __ex_table construction Jisheng Zhang
2021-10-18 0:14 ` kernel test robot
2021-10-20 14:03 ` Jisheng Zhang
2021-10-16 16:05 ` [PATCH 2/2] riscv: switch to relative exception tables 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=20211017000408.4ae9ecd6@xhacker \
--to=jszhang3@mail.ustc.edu.cn \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
--cc=ndesaulniers@google.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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