From: Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>
To: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: jlee@suse.com, bp@alien8.de, ricardo.neri@intel.com,
matt@codeblueprint.co.uk, ard.biesheuvel@linaro.org,
ravi.v.shankar@intel.com, fenghua.yu@intel.com,
Sai Praneeth <sai.praneeth.prakhya@intel.com>
Subject: [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86
Date: Tue, 6 Dec 2016 11:15:59 -0800 [thread overview]
Message-ID: <1481051763-8705-1-git-send-email-sai.praneeth.prakhya@intel.com> (raw)
From: Sai Praneeth <sai.praneeth.prakhya@intel.com>
UEFI v2.6 introduces EFI_MEMORY_ATTRIBUTES_TABLE which describes memory
protections that may be applied to EFI Runtime code and data regions by
kernel. This helps kernel to map efi runtime regions more strictly and
hence allowing only appropriate accesses to these regions. Please refer
to "EFI_MEMORY_ATTRIBUTES_TABLE" in section 4.6 of UEFI specification
v2.6 for more information on this table.
This patch set relies on commit a604af075a32 ("efi: Add support for the
EFI_MEMORY_ATTRIBUTES_TABLE config table"), commit 10f0d2f57705 ("efi:
Implement generic support for the Memory Attributes table") and hence
implements support for only x86.
Since the above commits have already implemented early discovery and
validation of table, the following patches implement a call back
function for x86 which is called only when EFI_MEMORY_ATTRIBUTES_TABLE
is detected.
Patch #1 makes the efi_memory_attributes table detection code generic
across all architectures
Patch #2 adds EFI_MEM_ATTR bit to keep track of this feature
Patch #3 Implements call back function that does stricter mappings based
on this table
Patch #4 Skip parsing of EFI_PROPERTIES_TABLE if EFI_MEMORY_ATTRIBUTES_TABLE
is detected
Sai Praneeth (4):
efi: Make EFI_MEMORY_ATTRIBUTES_TABLE initialization common across all
architectures
efi: Introduce EFI_MEM_ATTR bit and set it from memory attributes
table
x86/efi: Add support for EFI_MEMORY_ATTRIBUTES_TABLE
efi: Skip parsing of EFI_PROPERTIES_TABLE if
EFI_MEMORY_ATTRIBUTES_TABLE is detected
arch/x86/platform/efi/efi_64.c | 64 ++++++++++++++++++++++++++++++++++-------
drivers/firmware/efi/arm-init.c | 1 -
drivers/firmware/efi/efi.c | 13 +++++++++
drivers/firmware/efi/memattr.c | 6 +++-
include/linux/efi.h | 1 +
5 files changed, 73 insertions(+), 12 deletions(-)
--
2.1.4
next reply other threads:[~2016-12-06 19:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 19:15 Sai Praneeth Prakhya [this message]
2016-12-06 19:16 ` [PATCH 1/4] efi: Make EFI_MEMORY_ATTRIBUTES_TABLE initialization common across all architectures Sai Praneeth Prakhya
2016-12-07 13:28 ` Matt Fleming
2016-12-06 19:16 ` [PATCH 2/4] efi: Introduce EFI_MEM_ATTR bit and set it from memory attributes table Sai Praneeth Prakhya
2016-12-06 19:16 ` [PATCH 3/4] x86/efi: Add support for EFI_MEMORY_ATTRIBUTES_TABLE Sai Praneeth Prakhya
2016-12-06 19:16 ` [PATCH 4/4] efi: Skip parsing of EFI_PROPERTIES_TABLE if EFI_MEMORY_ATTRIBUTES_TABLE is detected Sai Praneeth Prakhya
2016-12-07 13:36 ` Matt Fleming
2016-12-07 13:26 ` [PATCH 0/4] UEFI: EFI_MEMORY_ATTRIBUTES_TABLE support for x86 Matt Fleming
2016-12-07 13:56 ` Matt Fleming
2016-12-07 19:01 ` Sai Praneeth Prakhya
2016-12-07 20:04 ` Matt Fleming
2016-12-07 20:13 ` Sai Praneeth Prakhya
2016-12-13 6:47 ` joeyli
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=1481051763-8705-1-git-send-email-sai.praneeth.prakhya@intel.com \
--to=sai.praneeth.prakhya@intel.com \
--cc=ard.biesheuvel@linaro.org \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=jlee@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri@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®