From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753388AbXDBHmP (ORCPT ); Mon, 2 Apr 2007 03:42:15 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753391AbXDBHmP (ORCPT ); Mon, 2 Apr 2007 03:42:15 -0400 Received: from e34.co.us.ibm.com ([32.97.110.152]:43433 "EHLO e34.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753388AbXDBHmO (ORCPT ); Mon, 2 Apr 2007 03:42:14 -0400 Date: Mon, 2 Apr 2007 13:11:59 +0530 From: Vivek Goyal To: Andrew Morton Cc: "Eric W. Biederman" , Jurriaan , Helge Hafting , linux-kernel@vger.kernel.org Subject: Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned" Message-ID: <20070402074159.GA13704@in.ibm.com> Reply-To: vgoyal@in.ibm.com References: <20070330010559.2a232d9a.akpm@linux-foundation.org> <20070331071220.GA26910@aitel.hist.no> <20070331005303.354411f0.akpm@linux-foundation.org> <20070401052932.GA9894@amd64.of.nowhere> <20070331232957.e1c93f19.akpm@linux-foundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070331232957.e1c93f19.akpm@linux-foundation.org> User-Agent: Mutt/1.5.11 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Sat, Mar 31, 2007 at 11:29:57PM -0700, Andrew Morton wrote: > On Sun, 01 Apr 2007 00:15:51 -0600 ebiederm@xmission.com (Eric W. Biederman) wrote: > > > Does anyone know how to express the constraint of a 2M aligned number in Kconfig? > > Nope, but we could make CONFIG_PHYSICAL_START be in units of 2MB, which > would be a bit hard to use. > > Adding a BUILD_BUG_ON which checks this constraint might help. Plus a > useful comment right at the BUILD_BUG_ON site explaining what to do about > it. How about attached patch? Thanks Vivek o X86_64 kernel should run from 2MB aligned address for two reasons. - Performance. - For relocatable kernels, page tables are updated based on difference between compile time address and load time physical address. This difference should be multiple of 2MB as kernel text and data is mapped using 2MB pages and PMD should be pointing to a 2MB aligned address. Life is simpler if both compile time and load time kernel addresses are 2MB aligned. o Flag the error at compile time if one is trying to build a kernel which does not meet alignment restrictions. Signed-off-by: Vivek Goyal --- arch/x86_64/kernel/head64.c | 8 ++++++++ include/asm-x86_64/page.h | 1 + 2 files changed, 9 insertions(+) diff -puN arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M arch/x86_64/kernel/head64.c --- linux-2.6.21-rc5-mm3-vanilla/arch/x86_64/kernel/head64.c~x86_64-check-for-config-physical-start-aligned-2M 2007-04-02 20:46:43.000000000 +0530 +++ linux-2.6.21-rc5-mm3-vanilla-root/arch/x86_64/kernel/head64.c 2007-04-02 21:20:45.000000000 +0530 @@ -62,6 +62,14 @@ void __init x86_64_start_kernel(char * r { int i; + /* + * Make sure kernel is aligned to 2MB address. Catching it at compile + * time is better. Change your config file and compile the kernel + * for a 2MB aligned address (CONFIG_PHYSICAL_START) + */ + BUILD_BUG_ON(ALIGN(CONFIG_PHYSICAL_START, __KERNEL_ALIGN) + != CONFIG_PHYSICAL_START); + /* clear bss before set_intr_gate with early_idt_handler */ clear_bss(); diff -puN include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M include/asm-x86_64/page.h --- linux-2.6.21-rc5-mm3-vanilla/include/asm-x86_64/page.h~x86_64-check-for-config-physical-start-aligned-2M 2007-04-02 20:50:55.000000000 +0530 +++ linux-2.6.21-rc5-mm3-vanilla-root/include/asm-x86_64/page.h 2007-04-02 20:51:34.000000000 +0530 @@ -79,6 +79,7 @@ extern unsigned long phys_base; #endif /* !__ASSEMBLY__ */ #define __PHYSICAL_START CONFIG_PHYSICAL_START +#define __KERNEL_ALIGN 0x200000 #define __START_KERNEL (__START_KERNEL_map + __PHYSICAL_START) #define __START_KERNEL_map 0xffffffff80000000 #define __PAGE_OFFSET 0xffff810000000000 _