All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Jones <pjones@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Matthew Garrett <mjg@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: CONFIG_EFI should select CONFIG_RELOCATABLE
Date: Thu, 09 Jun 2011 10:41:17 -0400	[thread overview]
Message-ID: <4DF0DB8D.5080207@redhat.com> (raw)
In-Reply-To: <4DF0DAAB.7010005@zytor.com>

On 06/09/2011 10:37 AM, H. Peter Anvin wrote:
> On 06/09/2011 07:32 AM, Matthew Garrett wrote:
>> EFI doesn't provide any guarantees that any given address will be free,
>> so the bootloader must have the freedom to position the kernel
>> appropriately. Make CONFIG_EFI select CONFIG_RELOCATABLE in order to
>> ensure that this constraint is satisfiable.
>>
>> Signed-off-by: Matthew Garrett<mjg@redhat.com>
>> ---
>>   arch/x86/Kconfig |    1 +
>>   1 files changed, 1 insertions(+), 0 deletions(-)
>>
>> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
>> index da34972..580cd31 100644
>> --- a/arch/x86/Kconfig
>> +++ b/arch/x86/Kconfig
>> @@ -1454,6 +1454,7 @@ config ARCH_USES_PG_UNCACHED
>>   config EFI
>>   	bool "EFI runtime service support"
>>   	depends on ACPI
>> +	select RELOCATABLE
>>   	---help---
>>   	  This enables the kernel to use EFI runtime services that are
>>   	  available (such as the EFI variable services).
>
> Can we make this a depends on instead of select?

Seems weird to me - when you're configuring the kernel, you're more likely
to know that you want EFI than to remember that that requires relocation.

-- 
         Peter

  reply	other threads:[~2011-06-09 14:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-09 14:32 [PATCH] x86: CONFIG_EFI should select CONFIG_RELOCATABLE Matthew Garrett
2011-06-09 14:34 ` Peter Jones
2011-06-09 14:37 ` H. Peter Anvin
2011-06-09 14:41   ` Peter Jones [this message]
2011-06-09 15:23     ` H. Peter Anvin
2011-06-09 15:35       ` Matthew Garrett
2011-06-09 14:47   ` Matthew Garrett

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=4DF0DB8D.5080207@redhat.com \
    --to=pjones@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg@redhat.com \
    --cc=x86@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.