[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOAebxs5s3DKV8f+Zw+LFVB98PE6cs=RwcOH8qEiU_MPLM9RvQ@mail.gmail.com>
Date: Mon, 9 Oct 2017 14:59:09 -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
Hi Will,
> We have two table walks even with your patch series applied afaict: one in
> our definition of vmemmap_populate (arch/arm64/mm/mmu.c) and this one
> in the core code.
I meant to say implementing two new page table walkers, not at runtime.
> My worry is that these are actually highly arch-specific, but will likely
> grow more users in mm/ that assume things for all architectures that aren't
> necessarily valid.
I see, how about moving new kasan_map_populate() implementation into
arch dependent code:
arch/x86/mm/kasan_init_64.c
arch/arm64/mm/kasan_init.c
This way we won't need to add pmd_large()/pud_large() macros for arm64?
Pavel
Powered by blists - more mailing lists