lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sun, 29 Nov 2015 01:05:24 -0800 From: tip-bot for Matt Fleming <tipbot@...or.com> To: linux-tip-commits@...r.kernel.org Cc: sai.praneeth.prakhya@...el.com, ard.biesheuvel@...aro.org, hpa@...or.com, toshi.kani@...com, torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org, bp@...en8.de, mingo@...nel.org, tglx@...utronix.de, peterz@...radead.org, brgerst@...il.com, luto@...nel.org, sds@...ho.nsa.gov, akpm@...ux-foundation.org, bp@...e.de, luto@...capital.net, dvlasenk@...hat.com, davej@...emonkey.org.uk, matt@...eblueprint.co.uk Subject: [tip:x86/efi] Documentation/x86: Update EFI memory region description Commit-ID: ff3d0a12fb2dc123e2b46e9524ebf4e08de5c59c Gitweb: http://git.kernel.org/tip/ff3d0a12fb2dc123e2b46e9524ebf4e08de5c59c Author: Matt Fleming <matt@...eblueprint.co.uk> AuthorDate: Fri, 27 Nov 2015 21:09:35 +0000 Committer: Ingo Molnar <mingo@...nel.org> CommitDate: Sun, 29 Nov 2015 09:15:43 +0100 Documentation/x86: Update EFI memory region description Make it clear that the EFI page tables are only available during EFI runtime calls since that subject has come up a fair numbers of times in the past. Additionally, add the EFI region start and end addresses to the table so that it's possible to see at a glance where they fall in relation to other regions. Signed-off-by: Matt Fleming <matt@...eblueprint.co.uk> Reviewed-by: Borislav Petkov <bp@...e.de> Acked-by: Borislav Petkov <bp@...e.de> Cc: Andrew Morton <akpm@...ux-foundation.org> Cc: Andy Lutomirski <luto@...capital.net> Cc: Andy Lutomirski <luto@...nel.org> Cc: Ard Biesheuvel <ard.biesheuvel@...aro.org> Cc: Borislav Petkov <bp@...en8.de> Cc: Brian Gerst <brgerst@...il.com> Cc: Dave Jones <davej@...emonkey.org.uk> Cc: Denys Vlasenko <dvlasenk@...hat.com> Cc: H. Peter Anvin <hpa@...or.com> Cc: Linus Torvalds <torvalds@...ux-foundation.org> Cc: Peter Zijlstra <peterz@...radead.org> Cc: Sai Praneeth Prakhya <sai.praneeth.prakhya@...el.com> Cc: Stephen Smalley <sds@...ho.nsa.gov> Cc: Thomas Gleixner <tglx@...utronix.de> Cc: Toshi Kani <toshi.kani@...com> Cc: linux-efi@...r.kernel.org Link: http://lkml.kernel.org/r/1448658575-17029-7-git-send-email-matt@codeblueprint.co.uk Signed-off-by: Ingo Molnar <mingo@...nel.org> --- Documentation/x86/x86_64/mm.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/Documentation/x86/x86_64/mm.txt b/Documentation/x86/x86_64/mm.txt index 05712ac..c518dce 100644 --- a/Documentation/x86/x86_64/mm.txt +++ b/Documentation/x86/x86_64/mm.txt @@ -16,6 +16,8 @@ ffffec0000000000 - fffffc0000000000 (=44 bits) kasan shadow memory (16TB) ... unused hole ... ffffff0000000000 - ffffff7fffffffff (=39 bits) %esp fixup stacks ... unused hole ... +ffffffef00000000 - ffffffff00000000 (=64 GB) EFI region mapping space +... unused hole ... ffffffff80000000 - ffffffffa0000000 (=512 MB) kernel text mapping, from phys 0 ffffffffa0000000 - ffffffffff5fffff (=1525 MB) module mapping space ffffffffff600000 - ffffffffffdfffff (=8 MB) vsyscalls @@ -32,11 +34,9 @@ reference. Current X86-64 implementations only support 40 bits of address space, but we support up to 46 bits. This expands into MBZ space in the page tables. -->trampoline_pgd: - -We map EFI runtime services in the aforementioned PGD in the virtual -range of 64Gb (arbitrarily set, can be raised if needed) - -0xffffffef00000000 - 0xffffffff00000000 +We map EFI runtime services in the 'efi_pgd' PGD in a 64Gb large virtual +memory window (this size is arbitrary, it can be raised later if needed). +The mappings are not part of any other kernel PGD and are only available +during EFI runtime calls. -Andi Kleen, Jul 2004 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists