From: Maarten Lankhorst <maarten.lankhorst@canonical.com>
To: Olof Johansson <olof@lixom.net>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, mk@dee.su,
Marko Kohtala <marko.kohtala@gmail.com>,
Matt Fleming <matt.fleming@intel.com>,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH] x86: efi: Turn off efi_enabled after setup on mixed fw/kernel
Date: Mon, 20 Aug 2012 12:13:17 +0200 [thread overview]
Message-ID: <50320DBD.5080507@canonical.com> (raw)
In-Reply-To: <1345412920-10906-1-git-send-email-olof@lixom.net>
Hey,
Op 19-08-12 23:48, Olof Johansson schreef:
> When 32-bit EFI is used with 64-bit kernel (or vice versa), turn off
> efi_enabled once setup is done. Beyond setup, it is normally used to
> determine if runtime services are available and we will have none.
>
> This will resolve issues stemming from efivars modprobe panicking on a
> 32/64-bit setup, as well as some reboot issues on similar setups.
>
> Signed-off-by: Olof Johansson <olof@lixom.net>
> Cc: stable@kernel.org # 3.4 and 3.5
> Cc: Matt Fleming <matt.fleming@intel.com>
> Cc: Matthew Garrett <mjg@redhat.com>
> ---
> arch/x86/kernel/setup.c | 11 +++++++++++
> arch/x86/platform/efi/efi.c | 14 ++++++++------
> 2 files changed, 19 insertions(+), 6 deletions(-)
> <snip>
>
> +static inline bool efi_is_native(void)
> +{
> + return !(IS_ENABLED(CONFIG_X86_64) ^ efi_64bit);
> +}
>
Isn't this just a more complicated way of writing
IS_ENABLED(CONFIG_X86_64) == efi_64bit ?
Also moving the assignment to efi_init will make it no longer call
efi_reserve_boot_services, I don't know if that is intentional or not,
but something to consider at least since it's a behavioral change.
>From a quick glance with some grepping, efi reboot and efifb will
also no longer work, is that intentional?
~Maarten
next prev parent reply other threads:[~2012-08-20 10:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-19 21:48 Olof Johansson
2012-08-20 9:56 ` Matt Fleming
2012-08-20 10:13 ` Maarten Lankhorst [this message]
2012-08-20 21:59 ` Olof Johansson
2012-08-21 14:39 ` Matt Fleming
2012-08-21 14:53 ` H. Peter Anvin
2012-10-08 14:28 ` Matt Fleming
2012-10-24 6:24 ` [PATCH v2] " Olof Johansson
2012-10-24 8:40 ` Maarten Lankhorst
2012-10-24 15:21 ` Olof Johansson
2012-10-24 15:50 ` Maarten Lankhorst
2012-10-24 17:00 ` [PATCH v3] " Olof Johansson
2012-10-25 10:56 ` Matt Fleming
2012-10-25 13:20 ` Matt Fleming
2012-10-25 17:05 ` Olof Johansson
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=50320DBD.5080507@canonical.com \
--to=maarten.lankhorst@canonical.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marko.kohtala@gmail.com \
--cc=matt.fleming@intel.com \
--cc=mjg@redhat.com \
--cc=mk@dee.su \
--cc=olof@lixom.net \
/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