From: Matt Fleming <matt@console-pimps.org>
To: "Thomas Bächler" <thomas@archlinux.org>
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Matt Fleming <matt.fleming@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] efi: Clarify Kconfig help for EFI_MIXED
Date: Mon, 14 Apr 2014 10:33:32 +0100 [thread overview]
Message-ID: <20140414093332.GA10956@console-pimps.org> (raw)
In-Reply-To: <534B9C12.4050708@archlinux.org>
On Mon, 14 Apr, at 10:28:02AM, Thomas Bächler wrote:
> Am 14.04.2014 09:15, schrieb Ingo Molnar:
> >>> Right, it is really that it is not possible to boot a mixed-mode kernel
> >>> on its non-native firmware using the stub, since the stub itself can
> >>> only be one way or the other.
> >>
> >> Yeah, my help text was a bit... unhelpful.
> >>
> >> CONFIG_EFI_MIXED does not introduce a regression of any sort, you can
> >> enable it without worrying about that.
> >>
> >> All the boot configurations that used to work will continue to work.
> >>
> >> What I meant to say was that it isn't possible to use the EFI mixed
> >> *feature* (booting a 64-bit kernel with 32-bit firmware) with the
> >> EFI boot stub - so you can build support into your kernel but
> >> there's no way to make the CPU actually execute those code paths.
> >
> > Same goes for booting a 32-bit kernel on 64-bit firmware, right?
> >
>
> It seems that isn't implemented:
>
> config EFI_MIXED
> bool "EFI mixed-mode support"
> depends on EFI_STUB && X86_64
>
Correct, since that would require translating 64-bit pointers from the
firmware into 32-bit pointers for the kernel, which isn't as straight
forward as the 32-bit firmware / 64-bit kernel case, i.e. ensure all
allocations are < 4GB and truncate 64-bit pointers when they're passed
to the firmware.
That and the fact that no one has said "We really need support".
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-04-14 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 17:59 Thomas Bächler
2014-04-11 18:03 ` H. Peter Anvin
2014-04-11 18:44 ` Matt Fleming
2014-04-14 7:15 ` Ingo Molnar
2014-04-14 8:28 ` Thomas Bächler
2014-04-14 9:33 ` Matt Fleming [this message]
2014-04-14 9:47 ` Borislav Petkov
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=20140414093332.GA10956@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=thomas@archlinux.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome