From: Alex Ghiti <alex@ghiti.fr>
To: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
kasan-dev@googlegroups.com, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Cc: linux-arch@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/4] Kasan improvements and fixes
Date: Sun, 21 Feb 2021 08:42:08 -0500 [thread overview]
Message-ID: <24d45989-4f4e-281c-3f58-d492f0b582e9@ghiti.fr> (raw)
In-Reply-To: <20210208193017.30904-1-alex@ghiti.fr>
Hi,
Le 2/8/21 à 2:30 PM, Alexandre Ghiti a écrit :
> This small series contains some improvements for the riscv KASAN code:
>
> - it brings a better readability of the code (patch 1/2)
> - it fixes oversight regarding page table population which I uncovered
> while working on my sv48 patchset (patch 3)
> - it helps to have better performance by using hugepages when possible
> (patch 4)
>
> Alexandre Ghiti (4):
> riscv: Improve kasan definitions
> riscv: Use KASAN_SHADOW_INIT define for kasan memory initialization
> riscv: Improve kasan population function
> riscv: Improve kasan population by using hugepages when possible
>
> arch/riscv/include/asm/kasan.h | 22 +++++-
> arch/riscv/mm/kasan_init.c | 119 ++++++++++++++++++++++++---------
> 2 files changed, 108 insertions(+), 33 deletions(-)
>
I'm cc-ing linux-arch and linux-mm to get more chance to have reviewers
on this series.
Thanks,
Alex
next parent reply other threads:[~2021-02-21 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210208193017.30904-1-alex@ghiti.fr>
2021-02-21 13:42 ` Alex Ghiti [this message]
2021-02-23 2:58 ` Palmer Dabbelt
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=24d45989-4f4e-281c-3f58-d492f0b582e9@ghiti.fr \
--to=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--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