From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752216AbdHQJAq (ORCPT ); Thu, 17 Aug 2017 05:00:46 -0400 Received: from mail-wr0-f193.google.com ([209.85.128.193]:34627 "EHLO mail-wr0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751949AbdHQJAm (ORCPT ); Thu, 17 Aug 2017 05:00:42 -0400 Date: Thu, 17 Aug 2017 11:00:38 +0200 From: Ingo Molnar To: "Kirill A. Shutemov" Cc: Linus Torvalds , Andrew Morton , x86@kernel.org, Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andi Kleen , Dave Hansen , Andy Lutomirski , Michal Hocko , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCHv4 08/14] x86/mm: Make PGDIR_SHIFT and PTRS_PER_P4D variable Message-ID: <20170817090038.lfhmuk7hpuw2zzwo@gmail.com> References: <20170808125415.78842-1-kirill.shutemov@linux.intel.com> <20170808125415.78842-9-kirill.shutemov@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170808125415.78842-9-kirill.shutemov@linux.intel.com> User-Agent: NeoMutt/20170113 (1.7.2) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Kirill A. Shutemov wrote: > For boot-time switching between 4- and 5-level paging we need to be able > to fold p4d page table level at runtime. It requires variable > PGDIR_SHIFT and PTRS_PER_P4D. > > Signed-off-by: Kirill A. Shutemov > --- > arch/x86/boot/compressed/kaslr.c | 5 +++++ > arch/x86/include/asm/pgtable_32.h | 2 ++ > arch/x86/include/asm/pgtable_32_types.h | 2 ++ > arch/x86/include/asm/pgtable_64_types.h | 15 +++++++++++++-- > arch/x86/kernel/head64.c | 9 ++++++++- > arch/x86/mm/dump_pagetables.c | 12 +++++------- > arch/x86/mm/init_64.c | 2 +- > arch/x86/mm/kasan_init_64.c | 2 +- > arch/x86/platform/efi/efi_64.c | 4 ++-- > include/asm-generic/5level-fixup.h | 1 + > include/asm-generic/pgtable-nop4d.h | 1 + > include/linux/kasan.h | 2 +- > mm/kasan/kasan_init.c | 2 +- > 13 files changed, 43 insertions(+), 16 deletions(-) So I'm wondering what the code generation effect of this is - what's the before/after vmlinux size? My guess is that the effect should be very small, as these constants are not widely used - but I'm only guessing and could be wrong. Thanks, Ingo