From: Christophe Leroy <christophe.leroy@c-s.fr>
To: Daniel Axtens <dja@axtens.net>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linuxppc-dev@lists.ozlabs.org, kasan-dev@googlegroups.com,
aneesh.kumar@linux.ibm.com, bsingharora@gmail.com
Subject: Re: [PATCH v5 0/4] KASAN for powerpc64 radix
Date: Thu, 16 Jan 2020 10:34:05 +0100 [thread overview]
Message-ID: <8a1b7f4b-de14-90fe-2efa-789882d28702@c-s.fr> (raw)
In-Reply-To: <20200109070811.31169-1-dja@axtens.net>
Le 09/01/2020 à 08:08, Daniel Axtens a écrit :
> Building on the work of Christophe, Aneesh and Balbir, I've ported
> KASAN to 64-bit Book3S kernels running on the Radix MMU.
>
> This provides full inline instrumentation on radix, but does require
> that you be able to specify the amount of physically contiguous memory
> on the system at compile time. More details in patch 4.
This might be a stupid idea as I don't know ppc64 much. IIUC, PPC64
kernel can be relocated, there is no requirement to have it at address
0. Therefore, would it be possible to put the KASAN shadow mem at the
begining of the physical memory, instead of putting it at the end ?
That way, you wouldn't need to know the amount of memory at compile time
because KASAN shadow mem would always be at address 0.
Christophe
next prev parent reply other threads:[~2020-01-16 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 7:08 [PATCH v5 0/4] KASAN for powerpc64 radix Daniel Axtens
2020-01-09 7:08 ` [PATCH v5 1/4] kasan: define and use MAX_PTRS_PER_* for early shadow tables Daniel Axtens
2020-01-09 7:08 ` [PATCH v5 2/4] kasan: Document support on 32-bit powerpc Daniel Axtens
2020-01-09 7:08 ` [PATCH v5 3/4] powerpc/mm/kasan: rename kasan_init_32.c to init_32.c Daniel Axtens
2020-01-09 7:08 ` [PATCH v5 4/4] powerpc: Book3S 64-bit "heavyweight" KASAN support Daniel Axtens
2020-01-16 9:34 ` Christophe Leroy [this message]
2020-01-22 4:25 ` [PATCH v5 0/4] KASAN for powerpc64 radix Daniel Axtens
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=8a1b7f4b-de14-90fe-2efa-789882d28702@c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=aneesh.kumar@linux.ibm.com \
--cc=bsingharora@gmail.com \
--cc=dja@axtens.net \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).