public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-efi@vger.kernel.org" <linux-efi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Matt Fleming <matt.fleming@intel.com>
Subject: Re: RFC: default CONFIG_EFI_STUB=y
Date: Fri, 09 Aug 2013 08:38:43 -0700	[thread overview]
Message-ID: <52050D03.4030805@zytor.com> (raw)
In-Reply-To: <1376062345.2087.16.camel@dabdike.int.hansenpartnership.com>

On 08/09/2013 08:32 AM, James Bottomley wrote:
> On Fri, 2013-08-09 at 08:23 -0700, H. Peter Anvin wrote:
>> I would like to change the defaults for CONFIG_EFI and CONFIG_EFI_STUB
>> to y.  There is little reason to omit this since EFI now is a
>> significant percentage of all systems.
> 
> You didn't actually attach the patch, but I presume this is for 64 bit
> compiles on x86 only?  We still have significant problems getting 64 bit
> EFI to interact with 32 bit kernels, so I don't believe we should enable
> CONFIG_EFI globally for all of x86.
> 

Well, it doesn't *solve* the problem with cross-mode, but it should work
as-is for EFI32->32-bit kernel and EFI64->64-bit kernel.  For the
cross-mode kernels they will simply not do anything.

Either way, nothing bad should come from it.  The worst thing that will
happen is that the kernel says "I don't have any EFI that I recognize."

Cross-mode support will always require a secondary bootloader (since as
far as I know there is no concept of "fat binaries" for EFI), but Matt
Fleming is working on genuine cross-mode support for both the boot stub
and (eventually) run time support.

	-hpa


  reply	other threads:[~2013-08-09 15:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-09 15:23 RFC: default CONFIG_EFI_STUB=y H. Peter Anvin
2013-08-09 15:32 ` James Bottomley
2013-08-09 15:38   ` H. Peter Anvin [this message]
2013-08-13 18:30     ` H. Peter Anvin
2013-08-13 18:43       ` James Bottomley
2013-08-13 18:52         ` H. Peter Anvin
2013-08-13 19:02           ` James Bottomley
2013-08-13 19:06             ` H. Peter Anvin
2013-08-15  5:15         ` 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=52050D03.4030805@zytor.com \
    --to=hpa@zytor.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox