[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANpmjNMh9ef30N6LfTrKaAVFR5iKPt_pkKr9p4Ly=-BD7GbTQQ@mail.gmail.com>
Date: Wed, 16 Jun 2021 11:11:53 +0200
From: Marco Elver <elver@...gle.com>
To: Liu Shixin <liushixin2@...wei.com>
Cc: Paul Walmsley <paul.walmsley@...ive.com>,
Palmer Dabbelt <palmer@...belt.com>,
Palmer Dabbelt <palmerdabbelt@...gle.com>,
Albert Ou <aou@...s.berkeley.edu>,
Alexander Potapenko <glider@...gle.com>,
Dmitry Vyukov <dvyukov@...gle.com>,
linux-riscv@...ts.infradead.org,
LKML <linux-kernel@...r.kernel.org>,
kasan-dev <kasan-dev@...glegroups.com>
Subject: Re: [PATCH -next v2] riscv: Enable KFENCE for riscv64
On Tue, 15 Jun 2021 at 04:35, Liu Shixin <liushixin2@...wei.com> wrote:
> Add architecture specific implementation details for KFENCE and enable
> KFENCE for the riscv64 architecture. In particular, this implements the
> required interface in <asm/kfence.h>.
>
> KFENCE requires that attributes for pages from its memory pool can
> individually be set. Therefore, force the kfence pool to be mapped at
> page granularity.
>
> Testing this patch using the testcases in kfence_test.c and all passed.
>
> Signed-off-by: Liu Shixin <liushixin2@...wei.com>
> Acked-by: Marco Elver <elver@...gle.com>
> Reviewed-by: Kefeng Wang <wangkefeng.wang@...wei.com>
I can't see this in -next yet. It would be nice if riscv64 could get
KFENCE support.
Thanks,
-- Marco
Powered by blists - more mailing lists