[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAOAebxvJDG0MasKMD-UovUgQyb+FP_4uXk5jV8Tsm9gopM_bUA@mail.gmail.com>
Date: Mon, 9 Oct 2017 15:57:38 -0400
From: Pavel Tatashin <pasha.tatashin@...cle.com>
To: Will Deacon <will.deacon@....com>
Cc: Mark Rutland <mark.rutland@....com>, catalin.marinas@....com,
linux-kernel@...r.kernel.org, sparclinux@...r.kernel.org,
linux-mm@...ck.org, linuxppc-dev@...ts.ozlabs.org,
linux-s390@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
x86@...nel.org, kasan-dev@...glegroups.com, borntraeger@...ibm.com,
heiko.carstens@...ibm.com, davem@...emloft.net,
willy@...radead.org, mhocko@...nel.org,
Ard Biesheuvel <ard.biesheuvel@...aro.org>, sam@...nborg.org,
mgorman@...hsingularity.net,
Steve Sistare <steven.sistare@...cle.com>,
daniel.m.jordan@...cle.com, bob.picco@...cle.com
Subject: Re: [PATCH v9 09/12] mm/kasan: kasan specific map populate function
>> I guess we could implement that on arm64 using our current vmemmap_populate
>> logic and an explicit memset.
Hi Will,
I will send out a new patch series with x86/arm64 versions of
kasan_map_populate(), so you could take a look if this is something
that is acceptable.
Thank you,
Pavel
Powered by blists - more mailing lists