|
Message-ID: <CAFTCetT5NcYNop_+X8rnC=pVarBQ=0AGoon7KH-NJq3v3qL8yA@mail.gmail.com> Date: Mon, 17 Apr 2017 10:18:09 +0530 From: Bhupesh SHARMA <bhupesh.linux@...il.com> To: Balbir Singh <bsingharora@...il.com> Cc: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>, Bhupesh Sharma <bhsharma@...hat.com>, Kees Cook <keescook@...omium.org>, kernel-hardening@...ts.openwall.com, Alistair Popple <alistair@...ple.id.au>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Scott Wood <oss@...error.net>, Paul Mackerras <paulus@...ba.org>, Alexander Graf <agraf@...e.com>, Daniel Cashman <dcashman@...roid.com>, Anatolij Gustschin <agust@...x.de>, "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)" <linuxppc-dev@...ts.ozlabs.org>, Daniel Cashman <dcashman@...gle.com> Subject: Re: [PATCH v3] powerpc: mm: support ARCH_MMAP_RND_BITS On Thu, Apr 13, 2017 at 12:39 PM, Balbir Singh <bsingharora@...il.com> wrote: >>> >>> Yes. It was derived from TASK_SIZE : >>> >>> http://lxr.free-electrons.com/source/arch/powerpc/include/asm/processor.h#L105 >>> >> >> That is getting update to 128TB by default and conditionally to 512TB >> > > Since this is compile time, we should probably keep the scope to 128TB > for now and see if we want to change things at run time later, since > the expansion is based on a hint. Suggestions? > I think this makes sense. If the conditional expansion to 512TB is protected by a kconfig symbol, we can use the same to have separate ranges for 128TB and 512TB using the kconfig symbol as the differentiating factor. Also please let me know which branch/tree to use where we are done with the change making the default to 128TB. My v2 was based on git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git (mater branch), where the TASK_SIZE is set to 46-bits inside 'arch/powerpc/include/asm/processor.h'. So that I can spin the v3 accordingly. Thanks, Bhupesh
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.