[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <7a68d7b8-7c16-3646-c191-e28d46fe2e53@huawei.com>
Date: Fri, 22 Oct 2021 08:46:51 +0800
From: Kefeng Wang <wangkefeng.wang@...wei.com>
To: Jisheng Zhang <jszhang3@...l.ustc.edu.cn>,
Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Albert Ou <aou@...s.berkeley.edu>,
Masahiro Yamada <masahiroy@...nel.org>,
Michal Marek <michal.lkml@...kovi.net>,
Nick Desaulniers <ndesaulniers@...gle.com>
CC: <linux-riscv@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<linux-kbuild@...r.kernel.org>
Subject: Re: [PATCH v3 0/2] riscv: switch to relative extable
On 2021/10/22 0:19, Jisheng Zhang wrote:
> From: Jisheng Zhang <jszhang@...nel.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.
Reviewed-by: Kefeng Wang <wangkefeng.wang@...wei.com>
Powered by blists - more mailing lists