From: Andi Kleen <ak@halobates.de>
To: Vegard Nossum <vegard.nossum@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Huang Ying <ying.huang@intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: revert CONFIG_RELOCATABLE=y defconfig change
Date: Fri, 19 Dec 2008 12:32:27 +0100 [thread overview]
Message-ID: <87vdtgz9h0.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20081218173506.GA29781@localhost.localdomain> (Vegard Nossum's message of "Thu, 18 Dec 2008 18:35:06 +0100")
Vegard Nossum <vegard.nossum@gmail.com> writes:
> From 37a92bc970ce025d8a42fed27413485fd341db31 Mon Sep 17 00:00:00 2001
> From: Vegard Nossum <vegard.nossum@gmail.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@elte.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@linux.intel.com
next prev parent reply other threads:[~2008-12-19 11:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 17:35 [PATCH] x86: revert CONFIG_RELOCATABLE=y defconfig change Vegard Nossum
2008-12-18 19:57 ` Ingo Molnar
2008-12-19 11:32 ` Andi Kleen [this message]
2008-12-19 16:18 ` H. Peter Anvin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vdtgz9h0.fsf@basil.nowhere.org \
--to=ak@halobates.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=vegard.nossum@gmail.com \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox