[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1519764469.2693.4.camel@hpe.com>
Date: Tue, 27 Feb 2018 20:02:45 +0000
From: "Kani, Toshi" <toshi.kani@....com>
To: "will.deacon@....com" <will.deacon@....com>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linuxarm@...wei.com" <linuxarm@...wei.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"guohanjun@...wei.com" <guohanjun@...wei.com>,
"wxf.wang@...ilicon.com" <wxf.wang@...ilicon.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"mark.rutland@....com" <mark.rutland@....com>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"cpandya@...eaurora.org" <cpandya@...eaurora.org>,
"Hocko, Michal" <mhocko@...e.com>,
"hanjun.guo@...aro.org" <hanjun.guo@...aro.org>
Subject: Re: 答复: [RFC patch] ioremap: don't set up huge I/O mappings when p4d/pud/pmd is zero
On Tue, 2018-02-27 at 19:59 +0000, Will Deacon wrote:
> On Tue, Feb 27, 2018 at 07:49:42PM +0000, Kani, Toshi wrote:
> > On Mon, 2018-02-26 at 20:53 +0800, Hanjun Guo wrote:
> > > On 2018/2/26 19:04, Will Deacon wrote:
> > > > On Mon, Feb 26, 2018 at 06:57:20PM +0800, Hanjun Guo wrote:
> > > > > Simply do something below at now (before the broken code is fixed)?
> > > > >
> > > > > diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> > > > > index b2b95f7..a86148c 100644
> > > > > --- a/arch/arm64/Kconfig
> > > > > +++ b/arch/arm64/Kconfig
> > > > > @@ -84,7 +84,6 @@ config ARM64
> > > > > select HAVE_ALIGNED_STRUCT_PAGE if SLUB
> > > > > select HAVE_ARCH_AUDITSYSCALL
> > > > > select HAVE_ARCH_BITREVERSE
> > > > > - select HAVE_ARCH_HUGE_VMAP
> > > > > select HAVE_ARCH_JUMP_LABEL
> > > > > select HAVE_ARCH_KASAN if !(ARM64_16K_PAGES && ARM64_VA_BITS_48)
> > > > > select HAVE_ARCH_KGDB
> > > >
> > > > No, that actually breaks with the use of block mappings for the kernel
> > > > text. Anyway, see:
> > > >
> > > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=15122ee2c515a253b0c66a3e618bc7ebe35105eb
> > >
> > > Sorry, just back from holidays and didn't catch up with all the emails,
> > > thanks for taking care of this.
> >
> > I will work on a fix for the common/x86 code.
>
> Ace, thanks. I'm more than happy to review any changes you make to the core
> code from a break-before-make perspective. Just stick me on cc.
Thanks Will! I will definitely keep you cc'd.
-Toshi
Powered by blists - more mailing lists