From: Daniel Axtens <dja@axtens.net>
To: Christophe Leroy <christophe.leroy@c-s.fr>,
aneesh.kumar@linux.ibm.com, bsingharora@gmail.com
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K . V" <aneesh.kumar@linux.vnet.ibm.com>,
kasan-dev@googlegroups.com
Subject: Re: [RFC PATCH 3/5] kasan: allow architectures to provide an outline readiness check
Date: Tue, 26 Feb 2019 11:14:10 +1100 [thread overview]
Message-ID: <87imx72yp9.fsf@dja-thinkpad.axtens.net> (raw)
In-Reply-To: <4ff60641-684a-8e86-0193-ef5380602096@c-s.fr>
>>> Unless somebody minds, I'll do the change and take this patch in my
>>> series in order to handle the case of book3s/32 hash.
>>
>> Please do; feel free to take as many of the patches as you would like
>> and I'll rebase whatever is left on the next version of your series.
>
> I have now done a big step with v7: works on both nohash and hash ppc32
> without any special feature in the core of kasan. Have to do more tests
> on the hash version, but it seems promissing.
>
> I have kept your patches on sync on top of it (allthough totally
> untested), you can find them in
> https://github.com/chleroy/linux/commits/kasan
Thanks - I've got sidetracked with other internal stuff but I hope to
get back to this later in the week.
Regards,
Daniel
>
>>
>> The idea with the macro magic was to take advantage of the speed of
>> static keys (I think, I borrowed it from Balbir's patch). Perhaps an
>> inline function will achieve this anyway, but given that KASAN with
>> outline instrumentation is inevitably slow, I guess it doesn't matter
>> much either way.
>
> You'll see in the modifications I've done to your patches, we can still
> use static keys while using static inline functions.
>
> Christophe
next prev parent reply other threads:[~2019-02-26 0:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:04 [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Daniel Axtens
2019-02-15 0:04 ` [RFC PATCH 1/5] kasan: do not open-code addr_has_shadow Daniel Axtens
2019-02-15 0:12 ` Andrew Donnellan
2019-02-15 8:21 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 2/5] kasan: allow architectures to manage the memory-to-shadow mapping Daniel Axtens
2019-02-15 6:35 ` Dmitry Vyukov
2019-02-15 0:04 ` [RFC PATCH 3/5] kasan: allow architectures to provide an outline readiness check Daniel Axtens
2019-02-15 8:25 ` Dmitry Vyukov
2019-02-17 12:05 ` christophe leroy
2019-02-18 6:13 ` Daniel Axtens
2019-02-25 14:01 ` Christophe Leroy
2019-02-26 0:14 ` Daniel Axtens [this message]
2019-02-15 0:04 ` [RFC PATCH 4/5] powerpc: move KASAN into its own subdirectory Daniel Axtens
2019-02-15 0:24 ` Andrew Donnellan
2019-02-17 16:29 ` christophe leroy
2019-02-18 9:14 ` Michael Ellerman
2019-02-18 12:27 ` Christophe Leroy
2019-02-19 0:44 ` Michael Ellerman
2019-02-15 0:04 ` [RFC PATCH 5/5] powerpc: KASAN for 64bit Book3E Daniel Axtens
2019-02-15 8:28 ` Dmitry Vyukov
2019-02-19 6:37 ` Daniel Axtens
2019-02-17 14:06 ` christophe leroy
2019-02-18 19:26 ` Christophe Leroy
2019-02-19 0:14 ` Daniel Axtens
2019-02-15 16:39 ` [RFC PATCH 0/5] powerpc: KASAN for 64-bit Book3E Christophe Leroy
2019-02-17 6:34 ` Balbir Singh
2019-02-19 6:35 ` 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=87imx72yp9.fsf@dja-thinkpad.axtens.net \
--to=dja@axtens.net \
--cc=aneesh.kumar@linux.ibm.com \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bsingharora@gmail.com \
--cc=christophe.leroy@c-s.fr \
--cc=kasan-dev@googlegroups.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.