From: "H. Peter Anvin" <hpa@zytor.com>
To: Olof Johansson <olof@lixom.net>
Cc: Marko Kohtala <marko.kohtala@gmail.com>,
linux-kernel@vger.kernel.org, mjg@redhat.com
Subject: Re: [PATCH] efi: add efi_runtime state checking
Date: Wed, 27 Jun 2012 14:52:37 -0700 [thread overview]
Message-ID: <4FEB80A5.8020806@zytor.com> (raw)
In-Reply-To: <1340832957-7386-1-git-send-email-olof@lixom.net>
On 06/27/2012 02:35 PM, Olof Johansson wrote:
> This adds an efi_runtime variable indicating whether the
> efi runtime services are available. The only time they are
> expected to not be available is when a 32-bit kernel has been
> booted using 64-but EFI and vice versa.
>
> It also adds checking to the two locations where functions are
> called; x86 reboot and efivars.
>
OK, stupid question:
Why is this different from the efi_enabled variable, or rather: why is
it different from what the efi_enabled variable *should* be? If runtime
services aren't available the only "EFI" that is available to the kernel
are the data structures passed in, and those can be checked directly...
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
next prev parent reply other threads:[~2012-06-27 21:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 20:47 [PATCH] efivars: prevent Oops if efi_enabled but no EFI runtime Marko Kohtala
2012-06-17 23:00 ` Olof Johansson
2012-06-18 20:06 ` Marko Kohtala
2012-06-27 21:35 ` [PATCH] efi: add efi_runtime state checking Olof Johansson
2012-06-27 21:52 ` H. Peter Anvin [this message]
2012-06-28 17:02 ` Olof Johansson
2012-08-15 0:51 ` H. Peter Anvin
2012-08-18 13:39 ` Matt Fleming
2012-06-18 20:22 ` [PATCH] efivars: prevent Oops if efi_enabled but no EFI runtime 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=4FEB80A5.8020806@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marko.kohtala@gmail.com \
--cc=mjg@redhat.com \
--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 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.