[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87vdtgz9h0.fsf@basil.nowhere.org>
Date: Fri, 19 Dec 2008 12:32:27 +0100
From: Andi Kleen <ak@...obates.de>
To: Vegard Nossum <vegard.nossum@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, Huang Ying <ying.huang@...el.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: revert CONFIG_RELOCATABLE=y defconfig change
Vegard Nossum <vegard.nossum@...il.com> writes:
> From 37a92bc970ce025d8a42fed27413485fd341db31 Mon Sep 17 00:00:00 2001
> From: Vegard Nossum <vegard.nossum@...il.com>
> Date: Thu, 18 Dec 2008 18:03:20 +0100
> Subject: [PATCH] x86: revert CONFIG_RELOCATABLE=y defconfig change
>
> This commit:
>
> commit 5cb04df8d3f03e37a19f2502591a84156be71772
> Author: Ingo Molnar <mingo@...e.hu>
> Date: Sun May 4 19:49:04 2008 +0200
>
> x86: defconfig updates
>
> changed CONFIG_RELOCATABLE from n to y, which may lead to a mismatch
> between the vmlinux debug information and the runtime location of the
> kernel, even when the bootloader does not relocate the kernel.
>
> Revert the specific change. Works for me with GRUB and qemu.
>
> Reference: http://lkml.org/lkml/2008/11/25/243
it would be better to find some way to fix up the debug information
(perhaps this can be done with the right ld parameters?)
Changing defconfig doesn't really fix the problem because there will
be still lots of kernel configurations around with
CONFIG_RELOCATABLE=y
-Andi
--
ak@...ux.intel.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists