From: Matt Fleming <matt@console-pimps.org>
To: Steve Langasek <steve.langasek@canonical.com>,
Matthew Garrett <mjg59@srcf.ucam.org>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
"H. Peter Anvin" <hpa@zytor.com>, Olof Johansson <olof@lixom.net>,
Tony Luck <tony.luck@intel.com>,
Matt Fleming <matt.fleming@intel.com>
Subject: [RFC PATCH 0/2] EFI facilities bitfield
Date: Thu, 3 Jan 2013 13:18:03 +0000 [thread overview]
Message-ID: <1357219085-4312-1-git-send-email-matt@console-pimps.org> (raw)
From: Matt Fleming <matt.fleming@intel.com>
Various users expect different semantics from 'efi_enabled', and one
variable can't be all things to all users. Introduce an EFI facilities
bitfield, which informs users what EFI initialisation steps were
completed successfully (are the system/config tables mapped, can we
invoke runtime services, etc?) and allows users to clearly document
which pieces of EFI firmware functionality they're using.
The immediate motivation for this patch series is the bug report at,
https://bugzilla.kernel.org/show_bug.cgi?id=47121
Drivers need a new means of detecting whether they're running on an
EFI machine, as sadly the expression,
if (!efi_enabled)
hasn't been a sufficient condition for quite some time.
This series has only seen minimal runtime testing since it's an RFC
and is intended to start a discussion.
Matt Fleming (2):
efi: Make 'efi_enabled' a function to query EFI facilities
samsung-laptop: Disable on EFI hardware
arch/x86/include/asm/efi.h | 1 +
arch/x86/kernel/reboot.c | 2 +-
arch/x86/kernel/setup.c | 28 ++++++++---------
arch/x86/platform/efi/efi.c | 55 ++++++++++++++++++++--------------
drivers/acpi/osl.c | 2 +-
drivers/firmware/dmi_scan.c | 2 +-
drivers/firmware/efivars.c | 4 +--
drivers/firmware/iscsi_ibft_find.c | 2 +-
drivers/gpu/drm/radeon/radeon_device.c | 3 +-
drivers/platform/x86/ibm_rtl.c | 2 +-
drivers/platform/x86/samsung-laptop.c | 3 ++
drivers/scsi/isci/init.c | 2 +-
include/linux/efi.h | 24 +++++++++++----
init/main.c | 4 +--
14 files changed, 80 insertions(+), 54 deletions(-)
--
1.7.11.7
next reply other threads:[~2013-01-03 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-03 13:18 Matt Fleming [this message]
2013-01-03 13:18 ` [RFC PATCH 1/2] efi: Make 'efi_enabled' a function to query EFI facilities Matt Fleming
2013-01-03 17:41 ` H. Peter Anvin
2013-01-04 15:08 ` Tim Gardner
2013-01-04 16:15 ` Matt Fleming
2013-01-04 16:17 ` H. Peter Anvin
2013-01-04 16:42 ` Tim Gardner
2013-01-03 13:18 ` [RFC PATCH 2/2] samsung-laptop: Disable on EFI hardware Matt Fleming
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=1357219085-4312-1-git-send-email-matt@console-pimps.org \
--to=matt@console-pimps.org \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=mjg59@srcf.ucam.org \
--cc=olof@lixom.net \
--cc=steve.langasek@canonical.com \
--cc=tony.luck@intel.com \
/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
all inboxes | Powered by JetHome®