Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754595AbbK0JdE (ORCPT ); Fri, 27 Nov 2015 04:33:04 -0500 Received: from foss.arm.com ([217.140.101.70]:48637 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754046AbbK0Jc6 (ORCPT ); Fri, 27 Nov 2015 04:32:58 -0500 Date: Fri, 27 Nov 2015 09:32:50 +0000 From: Catalin Marinas To: Andrey Ryabinin Cc: Daniel Cashman , "open list:DOCUMENTATION" , Will Deacon , "linux-mm@kvack.org" , "H. Peter Anvin" , mingo , aarcange@redhat.com, Russell King , "Kirill A. Shutemov" , Jonathan Corbet , xypron.glpk@gmx.de, "x86@kernel.org" , hecmargi@upv.es, Mel Gorman , David Rientjes , Borislav Petkov , nnk@google.com, dzickus@redhat.com, Kees Cook , jpoimboe@redhat.com, Thomas Gleixner , Andrew Morton , linux-arm-kernel@lists.infradead.org, LKML , salyzyn@android.com, "Eric W. Biederman" , jeffv@google.com, Naoya Horiguchi , dcashman@google.com Subject: Re: [PATCH v3 3/4] arm64: mm: support ARCH_MMAP_RND_BITS. Message-ID: <20151127093249.GW3109@e104818-lin.cambridge.arm.com> References: <1447888808-31571-1-git-send-email-dcashman@android.com> <1447888808-31571-2-git-send-email-dcashman@android.com> <1447888808-31571-3-git-send-email-dcashman@android.com> <1447888808-31571-4-git-send-email-dcashman@android.com> <20151123150459.GD4236@arm.com> <56536114.1020305@android.com> <20151125120601.GC3109@e104818-lin.cambridge.arm.com> <56561C71.30602@android.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1361 Lines: 33 On Fri, Nov 27, 2015 at 11:36:30AM +0300, Andrey Ryabinin wrote: > 2015-11-25 23:39 GMT+03:00 Daniel Cashman : > > On 11/25/2015 04:06 AM, Catalin Marinas wrote: > >> For KASan, we ended up calculating KASAN_SHADOW_OFFSET in > >> arch/arm64/Makefile. What would the formula be for the above > >> ARCH_MMAP_RND_BITS_MAX? > > > > The general formula I used ended up being: > > _max = floor(log(TASK_SIZE)) - log(PAGE_SIZE) - 3 > > For kasan, we calculate KASAN_SHADOW_OFFSET in Makefile, because we need to use > that value in Makefiles. > > For ARCH_MMAP_RND_COMPAT_BITS_MIN/MAX I don't see a reason why it has > to be in Kconfig. > Can't we just use your formula to #define ARCH_MMAP_RND_COMPAT_BITS_* > in some arch header? Because there is another option, ARCH_MMAP_RND_BITS depending on EXPERT which uses the MIN/MAX range defined per architecture. Since it's an expert feature, we could as well ignore the MIN/MAX in Kconfig and just add BUILD_BUG_ON checks to the code. This way we could simply define them in C files. Alternatively, add arithmetics support to kbuild ;). -- Catalin -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/