From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] UEFI: memory attribute table support
Date: Wed, 30 Mar 2016 18:38:48 +0200 [thread overview]
Message-ID: <1459355933-13529-1-git-send-email-ard.biesheuvel@linaro.org> (raw)
This implements ARM/arm64 support for dealing with the UEFI memory attribute
table, which allows the OS to map UEFI Runtime Services regions with stricter
permissions.
I have tried to implement the early discovery and validation of the table
as generically as possible. I think it should be reusable on x86 as well,
but I haven't tried myself. Note that this also depends on the way we
deal with the reservation of BootServicesData regions going forward.
Note that for 32-bit ARM, this depends on [1], which addresses an issue
with memremap() on that architecture
Patches #1 and #2 implement support for the EFI_MEMORY_RO and EFI_MEMORY_XP
attributes, and as it turns out, this code supports both the (obsolete)
PropertiesTable and the new Memory Attributes table, so I moved them to the
beginning of the series.
Patch #3 adds the GUID and type definitions for the memory attributes table.
Patch #4 implements the generic handling of the table.
Patch #5 wires it up for ARM and arm64.
Changes since v1:
- incorporate feedback from Matt (patches #2 and #4)
- rebased onto v4.6-rc1
[1] http://thread.gmane.org/gmane.linux.ports.arm.kernel/488476
Ard Biesheuvel (5):
ARM: efi: apply strict permissons for UEFI Runtime Services regions
arm64: efi: apply strict permissons for UEFI Runtime Services regions
efi: add support for the EFI_MEMORY_ATTRIBUTES_TABLE config table
efi: implement generic support for the Memory Attributes table
arm*: efi: take the Memory Attributes table into account
arch/arm/include/asm/efi.h | 1 +
arch/arm/kernel/efi.c | 41 +++++
arch/arm64/include/asm/efi.h | 2 +
arch/arm64/kernel/efi.c | 54 +++++--
drivers/firmware/efi/Makefile | 2 +-
drivers/firmware/efi/arm-init.c | 1 +
drivers/firmware/efi/arm-runtime.c | 3 +
drivers/firmware/efi/efi.c | 2 +
drivers/firmware/efi/memattr.c | 170 ++++++++++++++++++++
include/linux/efi.h | 26 +++
10 files changed, 287 insertions(+), 15 deletions(-)
create mode 100644 drivers/firmware/efi/memattr.c
--
2.5.0
next reply other threads:[~2016-03-30 16:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-30 16:38 Ard Biesheuvel [this message]
2016-03-30 16:38 ` [PATCH v2 1/5] ARM: efi: apply strict permissons for UEFI Runtime Services regions Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 2/5] arm64: " Ard Biesheuvel
2016-05-18 0:40 ` Shanker Donthineni
2016-05-18 6:18 ` Ard Biesheuvel
2016-05-18 13:06 ` Shanker Donthineni
2016-05-18 13:08 ` Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 3/5] efi: add support for the EFI_MEMORY_ATTRIBUTES_TABLE config table Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 4/5] efi: implement generic support for the Memory Attributes table Ard Biesheuvel
2016-04-01 12:36 ` Ard Biesheuvel
2016-04-08 15:56 ` Matt Fleming
2016-04-11 14:09 ` Ard Biesheuvel
2016-04-12 19:57 ` Matt Fleming
2016-04-13 8:29 ` Ard Biesheuvel
2016-04-13 10:24 ` Matt Fleming
2016-04-13 10:24 ` Ard Biesheuvel
2016-03-30 16:38 ` [PATCH v2 5/5] arm*: efi: take the Memory Attributes table into account Ard Biesheuvel
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=1459355933-13529-1-git-send-email-ard.biesheuvel@linaro.org \
--to=ard.biesheuvel@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).