stable UEFI virtual mappings for kexec
v4 cover stable UEFI virtual mappings for kexec
This is v4 of the series to update the UEFI memory map handling for the arm64 architecture so that virtual mappings of UEFI Runtime Services are stable across kexec.
To de-risk the adoption of the subset of patches that are essential to get kexec working on UEFI systems, in this v4 I dropped all the patches related to the iomem resource table, /dev/mem permissions and memory attributes etc. These topics will be revisited asap in a separate series.
The primary changes with respect to v3 in the patches that were kept are:
- instead of reording the memory map so that part of it can double as input argument to SetVirtualAddressMap(), increase the allocation size for the memory map so that we can use some of it as scratch space and use that to prepare the input to SVAM() instead.
- added some acks
- rebased onto v3.19-rc1
NOTE: these changes trigger an issue on AMD Seattle that we (Mark Rutland and I) consider a firmware bug. It appears that, during the call to SVAM() (which is called with a 1:1 mapping as per the UEFI spec) the virtual mapping being installed is dereferenced prematurely. This went unnoticed in the original situation, as the virtual mappings were just kernel mappings that are always accessible. However, in the new situation, those mappings are only active during Runtime Service invocations, and performing any kind of access through them at any other time triggers a fault.
============== v1 blurb ==================
The main premise of these patches is that, in order to support kexec, we need to add code to the kernel that is able to deal with the state of the firmware after SetVirtualAddressMap() [SVAM] has been called. However, if we are going to deal with that anyway, why not make that the default state, and have only a single code path for both cases.
This means SVAM() needs to move to the stub, and hence the code that invents the virtual layout needs to move with it. The result is that the kernel proper is entered with the virt_addr members of all EFI_MEMORY_RUNTIME regions assigned, and the mapping installed into the firmware. The kernel proper needs to set up the page tables, and switch to them while performing the runtime services calls. Note that there is also an efi_to_phys() to translate the values of the fw_vendor and tables fields of the EFI system table. Again, this is something we need to do anyway under kexec, or we end up handing over state between one kernel and the next, which implies different code paths between non-kexec and kexec.
The layout is chosen such that it used the userland half of the virtual address space (TTBR0), which means no additional alignment or reservation is required to ensure that it will always be available.
One thing that may stand out is the reordering of the memory map. The reason for doing this is that we can use the same memory map as input to SVAM(). The alternative is allocating memory for it using boot services, but that clutters up the existing logic a bit between getting the memory map, populating the fdt, and loop again if it didn't fit.
Ard Biesheuvel (8):
arm64/mm: add explicit struct_mm argument to __create_mapping() arm64/mm: add create_pgd_mapping() to create private page tables
efi: split off remapping code from efi_config_init()
efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE arm64/efi: set EFI_ALLOC_ALIGN to 64 KB
arm64/efi: move SetVirtualAddressMap() to UEFI stub arm64/efi: remove free_boot_services() and friends arm64/efi: remove idmap manipulations from UEFI code
arch/arm64/include/asm/efi.h | 24 +- arch/arm64/include/asm/mmu.h | 5 +- arch/arm64/include/asm/pgtable.h | 5 + arch/arm64/kernel/efi.c | 360 ++++++++----------------- arch/arm64/kernel/setup.c | 2 +- arch/arm64/mm/mmu.c | 60 ++--- drivers/firmware/efi/efi.c | 49 ++-- drivers/firmware/efi/libstub/efi-stub-helper.c | 25 +- drivers/firmware/efi/libstub/fdt.c | 137 +++++++++- include/linux/efi.h | 2 + 10 files changed, 348 insertions(+), 321 deletions(-)
Signature · 1 line
1.8.3.2
PATCH v4 1/8 arm64/mm: add explicit struct_mm argument to __create_mapping()
Currently, swapper_pg_dir and idmap_pg_dir share the init_mm mm_struct instance. To allow the introduction of other pg_dir instances, for instance, for UEFI's mapping of Runtime Services, make the struct_mm instance an explicit argument that gets passed down to the pmd and pte instantiation functions. Note that the consumers (pmd_populate/pgd_populate) of the mm_struct argument don't actually inspect it, but let's fix it for correctness' sake.
--- arch/arm64/mm/mmu.c | 31 ++++++++++++++++--------------- 1 file changed, 16 insertions(+), 15 deletions(-)
arch/arm64/mm/mmu.c +16 -15
@@ -156,9 +156,9 @@ static void __init alloc_init_pte(pmd_t *pmd, unsigned long addr, }while (pte++, addr +=PAGE_SIZE , addr != end); } -static void __init alloc_init_pmd (pud_t *pud,unsigned long addr, -unsigned long end,phys_addr_t phys, -int map_io) +static void __init alloc_init_pmd (struct mm_struct *mm,pud_t *pud, +unsigned long addr,unsigned long end, +phys_addr_t phys,int map_io) {pmd_t *pmd;unsigned long next;
@@ -178,7 +178,7 @@ static void __init alloc_init_pmd(pud_t *pud, unsigned long addr,*/ if (pud_none (*pud) ||pud_bad (*pud)) { pmd =early_alloc (PTRS_PER_PMD *sizeof (pmd_t)); -pud_populate (&init_mm, pud, pmd); +pud_populate (mm, pud, pmd); } pmd =pmd_offset (pud, addr);
@@ -202,16 +202,16 @@ static void __init alloc_init_pmd(pud_t *pud, unsigned long addr, }while (pmd++, addr = next, addr != end); } -static void __init alloc_init_pud (pgd_t *pgd,unsigned long addr, -unsigned long end,phys_addr_t phys, -int map_io) +static void __init alloc_init_pud (struct mm_struct *mm,pgd_t *pgd, +unsigned long addr,unsigned long end, +phys_addr_t phys,int map_io) {pud_t *pud;unsigned long next;if (pgd_none (*pgd)) { pud =early_alloc (PTRS_PER_PUD *sizeof (pud_t)); -pgd_populate (&init_mm, pgd, pud); +pgd_populate (mm, pgd, pud); }BUG_ON (pgd_bad (*pgd));
@@ -240,7 +240,7 @@ static void __init alloc_init_pud(pgd_t *pgd, unsigned long addr,flush_tlb_all (); } }else { -alloc_init_pmd (pud, addr, next, phys, map_io); +alloc_init_pmd (mm, pud, addr, next, phys, map_io); } phys += next - addr; }while (pud++, addr = next, addr != end);
@@ -250,9 +250,9 @@ static void __init alloc_init_pud(pgd_t *pgd, unsigned long addr,* Create the page directory entries and any necessary page tables for the * mapping specified by 'md'. */ -static void __init __create_mapping (pgd_t *pgd,phys_addr_t phys, -unsigned long virt,phys_addr_t size, -int map_io) +static void __init __create_mapping (struct mm_struct *mm,pgd_t *pgd, +phys_addr_t phys,unsigned long virt, +phys_addr_t size,int map_io) {unsigned long addr, length, end, next;
@@ -262,7 +262,7 @@ static void __init __create_mapping(pgd_t *pgd, phys_addr_t phys, end = addr + length;do { next =pgd_addr_end (addr, end); -alloc_init_pud (pgd, addr, next, phys, map_io); +alloc_init_pud (mm, pgd, addr, next, phys, map_io); phys += next - addr; }while (pgd++, addr = next, addr != end); }
@@ -275,7 +275,8 @@ static void __init create_mapping(phys_addr_t phys, unsigned long virt, &phys, virt);return ; } -__create_mapping (pgd_offset_k (virt &PAGE_MASK ), phys, virt, size,0 ); +__create_mapping (&init_mm,pgd_offset_k (virt &PAGE_MASK ), phys, virt, + size,0 ); }void __init create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io)
@@ -284,7 +285,7 @@ void __init create_id_mapping(phys_addr_t addr, phys_addr_t size, int map_io)pr_warn ("BUG: not creating id mapping for %pa\n" , &addr);return ; } -__create_mapping (&idmap_pg_dir[pgd_index (addr)], +__create_mapping (&init_mm, &idmap_pg_dir[pgd_index (addr)], addr, addr, size, map_io); }
Signature · 1 line
1.8.3.2
PATCH v4 2/8 arm64/mm: add create_pgd_mapping() to create private page tables
In reply to Ard BiesheuvelFor UEFI, we need to install the memory mappings used for Runtime Services in a dedicated set of page tables. Add create_pgd_mapping(), which allows us to allocate and install those page table entries early.
--- arch/arm64/include/asm/mmu.h | 3 +++ arch/arm64/include/asm/pgtable.h | 5 +++++ arch/arm64/mm/mmu.c | 43 ++++++++++++++++++++-------------------- 3 files changed, 30 insertions(+), 21 deletions(-)
arch/arm64/include/asm/mmu.h +3 -0
@@ -33,5 +33,8 @@ extern void __iomem *early_io_map(phys_addr_t phys, unsigned long virt);extern void init_mem_pgprot (void );/* create an identity mapping for memory (or io if map_io is true) */ extern void create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io); +extern void create_pgd_mapping (struct mm_struct *mm,phys_addr_t phys, +unsigned long virt,phys_addr_t size, +pgprot_t prot);#endif
arch/arm64/include/asm/pgtable.h +5 -0
@@ -264,6 +264,11 @@ static inline pmd_t pte_pmd(pte_t pte)return __pmd (pte_val (pte)); } +static inline pgprot_t mk_sect_prot (pgprot_t prot) +{ +return __pgprot (pgprot_val (prot) & ~PTE_TABLE_BIT ); +} +/* * THP definitions. */
arch/arm64/mm/mmu.c +22 -21
108 lines not on this page · raw message
Signature · 1 line
1.8.3.2
PATCH v4 3/8 efi: split off remapping code from efi_config_init()
In reply to Ard BiesheuvelSplit of the remapping code from efi_config_init() so that the caller can perform its own remapping. This is necessary to correctly handle virtually remapped UEFI memory regions under kexec, as efi.systab will have been updated to a virtual address.
--- drivers/firmware/efi/efi.c | 49 +++++++++++++++++++++++++++++----------------- include/linux/efi.h | 2 ++ 2 files changed, 33 insertions(+), 18 deletions(-)
drivers/firmware/efi/efi.c +31 -18
@@ -293,9 +293,10 @@ static __init int match_config_table(efi_guid_t *guid,return 0 ; } -int __init efi_config_init (efi_config_table_type_t *arch_tables) +int __init efi_config_parse_tables (void *config_tables,int count, +efi_config_table_type_t *arch_tables) { -void *config_tables, *tablep; +void *tablep;int i, sz;if (efi_enabled (EFI_64BIT ))
@@ -303,19 +304,9 @@ int __init efi_config_init(efi_config_table_type_t *arch_tables)else sz =sizeof (efi_config_table_32_t); -/* -* Let's see what config tables the firmware passed to us. -*/ - config_tables =early_memremap (efi.systab->tables, - efi.systab->nr_tables * sz); -if (config_tables ==NULL ) { -pr_err ("Could not map Configuration table!\n" ); -return -ENOMEM ; - } - tablep = config_tables;pr_info ("" ); -for (i =0 ; i < efi.systab->nr_tables; i++) { +for (i =0 ; i < count; i++) {efi_guid_t guid;unsigned long table;
@@ -328,8 +319,6 @@ int __init efi_config_init(efi_config_table_type_t *arch_tables)if (table64 >>32 ) {pr_cont ("\n" );pr_err ("Table located above 4GB, disabling EFI.\n" ); -early_memunmap (config_tables, - efi.systab->nr_tables * sz);return -EINVAL ; }#endif
@@ -344,13 +333,37 @@ int __init efi_config_init(efi_config_table_type_t *arch_tables) tablep += sz; }pr_cont ("\n" ); -early_memunmap (config_tables, efi.systab->nr_tables * sz); -set_bit (EFI_CONFIG_TABLES , &efi.flags); -return 0 ; } +int __init efi_config_init (efi_config_table_type_t *arch_tables) +{ +void *config_tables; +int sz, ret; + +if (efi_enabled (EFI_64BIT )) + sz =sizeof (efi_config_table_64_t); +else + sz =sizeof (efi_config_table_32_t); + +/* +* Let's see what config tables the firmware passed to us. +*/ + config_tables =early_memremap (efi.systab->tables, + efi.systab->nr_tables * sz); +if (config_tables ==NULL ) { +pr_err ("Could not map Configuration table!\n" ); +return -ENOMEM ; + } + + ret =efi_config_parse_tables (config_tables, efi.systab->nr_tables, + arch_tables); + +early_memunmap (config_tables, efi.systab->nr_tables * sz); +return ret; +} +#ifdef CONFIG_EFI_VARS_MODULE static int __init efi_load_efivars (void ) {
include/linux/efi.h +2 -0
@@ -875,6 +875,8 @@ static inline efi_status_t efi_query_variable_store(u32 attributes, unsigned lon#endif extern void __iomem *efi_lookup_mapped_addr (u64 phys_addr);extern int efi_config_init (efi_config_table_type_t *arch_tables); +extern int efi_config_parse_tables (void *config_tables,int count, +efi_config_table_type_t *arch_tables);extern u64 efi_get_iobase (void );extern u32 efi_mem_type (unsigned long phys_addr);extern u64 efi_mem_attributes (unsigned long phys_addr);
Signature · 1 line
1.8.3.2
PATCH v4 3/8 efi: split off remapping code from efi_config_init()
Quoted 10 lines · Ard Biesheuvel
Split of the remapping code from
efi_config_init()so that the caller can perform its own remapping. This is necessary to correctly handle virtually remapped UEFI memory regions under kexec, as efi.systab will have been updated to a virtual address.Signed-off-by Ard Biesheuvel <[email protected]>--- drivers/firmware/efi/efi.c | 49 +++++++++++++++++++++++++++++----------------- include/linux/efi.h | 2 ++ 2 files changed, 33 insertions(+), 18 deletions(-)
Looks good Ard.
Signature · 1 line
Matt Fleming, Intel Open Source Technology Center
PATCH v4 3/8 efi: split off remapping code from efi_config_init()
In reply to Ard BiesheuvelQuoted 6 lines · Ard Biesheuvel
Split of the remapping code from
efi_config_init()so that the caller can perform its own remapping. This is necessary to correctly handle virtually remapped UEFI memory regions under kexec, as efi.systab will have been updated to a virtual address.Signed-off-by Ard Biesheuvel <[email protected]>
...
Quoted 23 lines
drivers/firmware/efi/efi.c +12
-3@@ -344,13 +333,37 @@ int __init efi_config_init(efi_config_table_type_t *arch_tables) tablep += sz; }pr_cont ("\n" ); -early_memunmap (config_tables, efi.systab->nr_tables * sz); -set_bit (EFI_CONFIG_TABLES , &efi.flags); -return 0 ; } +int __init efi_config_init (efi_config_table_type_t *arch_tables) +{ +void *config_tables; +int sz, ret; + +if (efi_enabled (EFI_64BIT )) + sz =sizeof (efi_config_table_64_t); +else + sz =sizeof (efi_config_table_32_t); + +/* +* Let's see what config tables the firmware passed to us.
drivers/firmware/efi/efi.c int __init efi_config_init(efi_config_table_type_t *arch_tables) · line 361
Quoted 10 lines
drivers/firmware/efi/efi.c +10
-0+*/ + config_tables =early_memremap (efi.systab->tables, + efi.systab->nr_tables * sz); +if (config_tables ==NULL ) { +pr_err ("Could not map Configuration table!\n" ); +return -ENOMEM ; + } + + ret =efi_config_parse_tables (config_tables, efi.systab->nr_tables, + arch_tables);
Just a nitpick:
You could hand down @sz to this function so that you don't have to compute it again in efi_config_parse_tables().
Signature · 5 lines
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--PATCH v4 4/8 efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE
In reply to Ard BiesheuvelOn systems with 64 KB pages, it is preferable for UEFI memory map entries to be 64 KB aligned multiples of 64 KB, because it relieves us of having to deal with the residues.
So, if EFI_ALLOC_ALIGN is #define'd by the platform, use it to round up all memory allocations made.
--- drivers/firmware/efi/libstub/efi-stub-helper.c | 25 +++++++++++++++++-------- 1 file changed, 17 insertions(+), 8 deletions(-)
drivers/firmware/efi/libstub/efi-stub-helper.c +17 -8
@@ -32,6 +32,15 @@static unsigned long __chunk_size =EFI_READ_CHUNK_SIZE ; +/* +* Allow the platform to override the allocation granularity: this allows +* systems that have the capability to run with a larger page size to deal +* with the allocations for initrd and fdt more efficiently. +*/ +#ifndef EFI_ALLOC_ALIGN +#define EFI_ALLOC_ALIGN EFI_PAGE_SIZE +#endif +struct file_info {efi_file_handle_t *handle;u64 size;
@@ -150,10 +159,10 @@ efi_status_t efi_high_alloc(efi_system_table_t *sys_table_arg,* a specific address. We are doing page-based allocations, * so we must be aligned to a page. */ -if (align <EFI_PAGE_SIZE ) - align =EFI_PAGE_SIZE ; +if (align <EFI_ALLOC_ALIGN ) + align =EFI_ALLOC_ALIGN ; - nr_pages =round_up (size,EFI_PAGE_SIZE ) /EFI_PAGE_SIZE ; + nr_pages =round_up (size,EFI_ALLOC_ALIGN ) /EFI_PAGE_SIZE ; again:for (i =0 ; i < map_size / desc_size; i++) {efi_memory_desc_t *desc;
@@ -235,10 +244,10 @@ efi_status_t efi_low_alloc(efi_system_table_t *sys_table_arg,* a specific address. We are doing page-based allocations, * so we must be aligned to a page. */ -if (align <EFI_PAGE_SIZE ) - align =EFI_PAGE_SIZE ; +if (align <EFI_ALLOC_ALIGN ) + align =EFI_ALLOC_ALIGN ; - nr_pages =round_up (size,EFI_PAGE_SIZE ) /EFI_PAGE_SIZE ; + nr_pages =round_up (size,EFI_ALLOC_ALIGN ) /EFI_PAGE_SIZE ;for (i =0 ; i < map_size / desc_size; i++) {efi_memory_desc_t *desc;unsigned long m = (unsigned long )map;
@@ -292,7 +301,7 @@ void efi_free(efi_system_table_t *sys_table_arg, unsigned long size,if (!size)return ; - nr_pages =round_up (size,EFI_PAGE_SIZE ) /EFI_PAGE_SIZE ; + nr_pages =round_up (size,EFI_ALLOC_ALIGN ) /EFI_PAGE_SIZE ;efi_call_early (free_pages, addr, nr_pages); }
@@ -561,7 +570,7 @@ efi_status_t efi_relocate_kernel(efi_system_table_t *sys_table_arg,* to the preferred address. If that fails, allocate as low * as possible while respecting the required alignment. */ - nr_pages =round_up (alloc_size,EFI_PAGE_SIZE ) /EFI_PAGE_SIZE ; + nr_pages =round_up (alloc_size,EFI_ALLOC_ALIGN ) /EFI_PAGE_SIZE ; status =efi_call_early (allocate_pages,EFI_ALLOCATE_ADDRESS ,EFI_LOADER_DATA , nr_pages, &efi_addr);
Signature · 1 line
1.8.3.2
PATCH v4 4/8 efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE
Quoted 8 lines · Ard Biesheuvel
On systems with 64 KB pages, it is preferable for UEFI memory map entries to be 64 KB aligned multiples of 64 KB, because it relieves us of having to deal with the residues.
So, ifEFI_ALLOC_ALIGNis #define'd by the platform, use it to round up all memory allocations made.Acked-by Matt Fleming <[email protected]>Signed-off-by Ard Biesheuvel <[email protected]>
Signature · 5 lines
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is fine.
--PATCH v4 4/8 efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE
Quoted 7 lines · Borislav Petkov
Quoted 6 lines · Ard Biesheuvel
On systems with 64 KB pages, it is preferable for UEFI memory map entries to be 64 KB aligned multiples of 64 KB, because it relieves us of having to deal with the residues.
So, ifEFI_ALLOC_ALIGNis #define'd by the platform, use it to round up all memory allocations made.
Quoted 5 lines
Quoted 2 lines
Acked-by Matt Fleming <[email protected]>Signed-off-by Ard Biesheuvel <[email protected]>Acked-by Borislav Petkov <[email protected]>
Thanks Boris.
Do you have any comments regarding patches #3 and #6 in this series? Patch #3 is actual common code, but patch #6 also touches a file under drivers/firmware/efi/libstub (but it is only used by arm64 atm) With your acks on those, I could ask Catalin or Will to take the whole series through the arm64 tree.
Regards,
Ard.
PATCH v4 4/8 efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE
Quoted 1 line · Ard Biesheuvel
Do you have any comments regarding patches #3 and #6 in this series?
Sorry, have had no time so far to take a look. Holidays and all... You're on the TODO list though :-)
Signature · 3 lines
Regards/Gruss,
Boris.
--PATCH v4 4/8 efi: efistub: allow allocation alignment larger than EFI_PAGE_SIZE
Quoted 6 lines · Borislav Petkov
Quoted 1 line · Ard Biesheuvel
Do you have any comments regarding patches #3 and #6 in this series?
Sorry, have had no time so far to take a look. Holidays and all... You're on the TODO list though :-)
No worries, business has been slow for everyone, I'm sure.
Regards,
Ard.
PATCH v4 5/8 arm64/efi: set EFI_ALLOC_ALIGN to 64 KB
In reply to Ard BiesheuvelSet EFI_ALLOC_ALIGN to 64 KB so that all allocations done by the stub are naturally compatible with a 64 KB granule kernel.
--- arch/arm64/include/asm/efi.h | 2 ++ 1 file changed, 2 insertions(+)
arch/arm64/include/asm/efi.h +2 -0
@@ -44,4 +44,6 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__) +#define EFI_ALLOC_ALIGN SZ_64K +#endif /* _ASM_EFI_H */
Signature · 1 line
1.8.3.2
PATCH v4 5/8 arm64/efi: set EFI_ALLOC_ALIGN to 64 KB
Quoted 21 lines · Ard Biesheuvel
Set
EFI_ALLOC_ALIGNto 64 KB so that all allocations done by the stub are naturally compatible with a 64 KB granule kernel.Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 2 ++ 1 file changed, 2 insertions(+)arch/arm64/include/asm/efi.h +2
-0@@ -44,4 +44,6 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__) +#define EFI_ALLOC_ALIGN SZ_64K +#endif /* _ASM_EFI_H */ Signature · 1 line
1.8.3.2
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
In reply to Ard BiesheuvelIn order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after SetVirtualAddressMap() has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call to SetVirtualAddressMap() to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.
This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)
arch/arm64/include/asm/efi.h +16 -4
@@ -7,28 +7,36 @@#ifdef CONFIG_EFI extern void efi_init (void );extern void efi_idmap_init (void ); +extern void efi_virtmap_init (void );#else #define efi_init ()#define efi_idmap_init () +#define efi_virtmap_init#endif #define efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ efi_status_t __s; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \ +efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \ __s =__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ __s; \ })#define __efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \ +efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ })
@@ -45,5 +53,9 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__)#define EFI_ALLOC_ALIGN SZ_64K +#define EFI_VIRTMAP EFI_ARCH_1 + +void efi_virtmap_load (void ); +void efi_virtmap_unload (void );#endif /* _ASM_EFI_H */
arch/arm64/kernel/efi.c +120 -103
302 lines not on this page · raw message
arch/arm64/kernel/setup.c +1 -0
@@ -402,6 +402,7 @@ void __init setup_arch(char **cmdline_p)request_standard_resources ();efi_idmap_init (); +efi_virtmap_init ();unflatten_device_tree ();
drivers/firmware/efi/libstub/fdt.c +133 -4
165 lines not on this page · raw message
Signature · 1 line
1.8.3.2
Mark Rutland
reviewerPATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Hi Ard,
I have a few (minor) comments below.
Quoted 22 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)
[...]
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 449
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+static void efi_set_pgd (struct mm_struct *mm) +{ +cpu_switch_mm (mm->pgd, mm); +flush_tlb_all (); +if (icache_is_aivivt ()) +__flush_icache_all (); +}
Do we have any idea how often we call runtime services?
I assume not all that often (read the RTC at boot, set/get variables).
If we're nuking the TLBs and I-cache a lot we'll probably need to reserve an asid for the EFI virtmap.
[...]
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+void __init efi_virtmap_init (void ) +{ +efi_memory_desc_t *md; + +if (!efi_enabled (EFI_BOOT )) +return ; +
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 478
Quoted 10 lines
arch/arm64/kernel/efi.c +10
-0+for_each_efi_memory_desc (&memmap, md) { +u64 paddr, npages, size; +pgprot_t prot; + +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; +if (WARN (md->virt_addr ==0 , +"UEFI virtual mapping incomplete or missing -- no entry found for 0x%llx\n" , + md->phys_addr)) +return ;
I wonder if we might want to use a different address to signal a bad mapping (e.g. 0UL-1 as it's not even EFI_PAGE_SIZE aligned), just in case we have to handle a valid use of zero in future for some reason -- perhaps coming from another OS.
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 485
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+ + paddr = md->phys_addr; + npages = md->num_pages; +memrange_efi_to_native (&paddr, &npages); + size = npages <<PAGE_SHIFT ; + + pr_info(" EFI remap 0x%012llx => %p\n",
Why not use %016llx? We might only have 48-bit PAs currently, but we may as well keep the VA and PA equally long when printing out -- that'll also help to identify issues with garbage in the upper 16 bits of the PA field.
[...]
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 214
Quoted 6 lines
drivers/firmware/efi/libstub/fdt.c +6
-0+/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000
Nit: I'm not keen on the term "userland" here. You can map stuff to EL0 in the high half of the address space if you wanted, so TTBR0/TTBR1 aren't architecturally user/kernel.
s/userland/low half/, perhaps?
It might also be worth pointing out that the arbitrary base address isn't zero so as to be less likely to be an idmap.
Quoted 32 lines
drivers/firmware/efi/libstub/fdt.c +32
-0+ +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M )
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 256
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+ efi_virt_base =round_up (efi_virt_base,SZ_2M ); + + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +}
This feels like this should live in arch/arm64, or under some other directory specific to arm/arm64. That said, I guess the fdt stuff is currently arm-specific anyway, so perhaps this is fine.
[...]
Quoted 5 lines
drivers/firmware/efi/libstub/fdt.c +1
-0@@ -248,12 +337,52 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, } } +/*
drivers/firmware/efi/libstub/fdt.c efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, · line 350
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+* Update the memory map with virtual addresses. The function will also +* populate the spare second half of the memory_map allocation with +* copies of just the EFI_MEMORY_RUNTIME entries so that we can pass it +* straight into SetVirtualAddressMap() +*/ +update_memory_map (memory_map, map_size, desc_size, + &runtime_entry_count); + +pr_efi (sys_table, +"Exiting boot services and installing virtual address map...\n" );
I believe that the memory map is allowed to change as a result of this call, so I think this needs to be moved before update_memory_map.
Thanks,
Mark.
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 30 lines · Mark Rutland
Hi Ard,
I have a few (minor) comments below.
Quoted 22 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)[...]
Quoted 9 lines
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 449
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+static void efi_set_pgd (struct mm_struct *mm) +{ +cpu_switch_mm (mm->pgd, mm); +flush_tlb_all (); +if (icache_is_aivivt ()) +__flush_icache_all (); +}Do we have any idea how often we call runtime services?
Very rarely.
Quoted 1 line
I assume not all that often (read the RTC at boot, set/get variables).
And in future possibly:
- adding capsules
- getwakeuptime/setwakeuptime
- saving time to RTC on shutdown
- reboot
All of which are uid0-invoked manual operations.
The only exception I can think of is if we're using the efivarfs backend for pstore.
Quoted 7 lines
If we're nuking the TLBs and I-cache a lot we'll probably need to reserve an asid for the EFI virtmap.
Quoted 4 lines
(quoted diff) +0
-0@@ -248,12 +337,52 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, } }
Quoted 14 lines
drivers/firmware/efi/libstub/fdt.c efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, · line 350
Quoted 11 lines
drivers/firmware/efi/libstub/fdt.c +11
-0+/* +* Update the memory map with virtual addresses. The function will also +* populate the spare second half of the memory_map allocation with +* copies of just the EFI_MEMORY_RUNTIME entries so that we can pass it +* straight into SetVirtualAddressMap() +*/ +update_memory_map (memory_map, map_size, desc_size, + &runtime_entry_count); + +pr_efi (sys_table, +"Exiting boot services and installing virtual address map...\n" );I believe that the memory map is allowed to change as a result of this call, so I think this needs to be moved before
update_memory_map.
You are absolutely correct - but update_memory_map() only modifies the copy of the memory map. The message needs to move all the way to before the calll to get_memory_map(), and for practical reasons perhaps before the while(1) loop.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
In reply to Mark RutlandQuoted 40 lines · Mark Rutland
Hi Ard,
I have a few (minor) comments below.
Quoted 22 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)[...]
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 449
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+static void efi_set_pgd (struct mm_struct *mm) +{ +cpu_switch_mm (mm->pgd, mm); +flush_tlb_all (); +if (icache_is_aivivt ()) +__flush_icache_all (); +}Do we have any idea how often we call runtime services?
Quoted 5 lines
I assume not all that often (read the RTC at boot, set/get variables).
If we're nuking the TLBs and I-cache a lot we'll probably need to reserve an asid for the EFI virtmap.
As pointed out by Leif, we should not be calling runtime services often enough for this to have an impact imo
Quoted 14 lines
Quoted 14 lines
arch/arm64/kernel/efi.c +14
-0+void __init efi_virtmap_init (void ) +{ +efi_memory_desc_t *md; + +if (!efi_enabled (EFI_BOOT )) +return ; + +for_each_efi_memory_desc (&memmap, md) { +u64 paddr, npages, size; +pgprot_t prot; + +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; + if (WARN(md->virt_addr == 0,
Quoted 9 lines
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 478
Quoted 3 lines
arch/arm64/kernel/efi.c +3
-0+"UEFI virtual mapping incomplete or missing -- no entry found for 0x%llx\n" , + md->phys_addr)) + return;I wonder if we might want to use a different address to signal a bad mapping (e.g. 0UL-1 as it's not even
EFI_PAGE_SIZEaligned), just in case we have to handle a valid use of zero in future for some reason -- perhaps coming from another OS.
The spec suggests that a failed call to SetVirtualAddressMap() means that the old 1:1 mapping is still in effect, and booting can continue as if the call was never made (This is suggested by the list of return codes, which are all based on validation of the input) That is also why efi_to_phys() returns the physical address if it doesn't find a virtual address, i.e., so that we can at least initialize EFI and the memory map. So afaict, there is really no reason to distinguish between 'SVAM() was not called' and 'SVAM() was called but didn't like its input args'.
Quoted 13 lines
arch/arm64/kernel/efi.c static int __init arm64_dmi_init(void) · line 485
Quoted 7 lines
arch/arm64/kernel/efi.c +7
-0+ + paddr = md->phys_addr; + npages = md->num_pages; +memrange_efi_to_native (&paddr, &npages); + size = npages <<PAGE_SHIFT ; + + pr_info(" EFI remap 0x%012llx => %p\n",Why not use %016llx? We might only have 48-bit PAs currently, but we may as well keep the VA and PA equally long when printing out -- that'll also help to identify issues with garbage in the upper 16 bits of the PA field.
Quoted 2 lines
[...]
Sure, why not. It is code I carried over from the previous version, but I am happy to change it here
Quoted 11 lines
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 214
Quoted 6 lines
drivers/firmware/efi/libstub/fdt.c +6
-0+/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000Nit: I'm not keen on the term "userland" here. You can map stuff to EL0 in the high half of the address space if you wanted, so TTBR0/TTBR1 aren't architecturally user/kernel.
Quoted 2 lines
s/userland/low half/, perhaps?
OK
Quoted 3 lines
It might also be worth pointing out that the arbitrary base address isn't zero so as to be less likely to be an idmap.
It is the largest non-zero base2 boundary that can reasonably be shared with v7, even with a 2:2 split.
I will add a comment to that effect.
Quoted 47 lines
Quoted 32 lines
drivers/firmware/efi/libstub/fdt.c +32
-0+ +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M )drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 256
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+ efi_virt_base =round_up (efi_virt_base,SZ_2M ); + + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +}This feels like this should live in
arch/arm64, or under some other directory specific to arm/arm64. That said, I guess the fdt stuff is currently arm-specific anyway, so perhaps this is fine.
Quoted 2 lines
[...]
I can move this function (and get_memory_map) to arm-stub.c instead.
Quoted 4 lines
Quoted 4 lines
(quoted diff) +0
-0@@ -248,12 +337,52 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, } }
Quoted 15 lines
drivers/firmware/efi/libstub/fdt.c efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, · line 350
Quoted 11 lines
drivers/firmware/efi/libstub/fdt.c +11
-0+/* +* Update the memory map with virtual addresses. The function will also +* populate the spare second half of the memory_map allocation with +* copies of just the EFI_MEMORY_RUNTIME entries so that we can pass it +* straight into SetVirtualAddressMap() +*/ +update_memory_map (memory_map, map_size, desc_size, + &runtime_entry_count); + +pr_efi (sys_table, +"Exiting boot services and installing virtual address map...\n" );I believe that the memory map is allowed to change as a result of this call, so I think this needs to be moved before
update_memory_map.
Yes, you mentioned that before but I forgot about it. I will fix that as well.
Signature · 1 line
Ard.
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
In reply to Ard BiesheuvelQuoted 22 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)
[...]
arch/arm64/include/asm/efi.h extern void efi_idmap_init(void); · line 56
Quoted 5 lines
arch/arm64/include/asm/efi.h +1
-0@@ -45,5 +53,9 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__)#define EFI_ALLOC_ALIGN SZ_64K +#define EFI_VIRTMAP EFI_ARCH_1
Any chance of documenting what EFI_VIRTMAP means for posterity and why you want to use one of the EFI arch config bits? How is this different from EFI_RUNTIME_SERVICES?
Take a look at EFI_OLD_MEMMAP in arch/x86/include/asm/efi.h for a crackingly well documented example from Borislav.
[...]
Quoted 36 lines
drivers/firmware/efi/libstub/fdt.c +28
-0@@ -167,6 +167,94 @@ fdt_set_fail:#define EFI_FDT_ALIGN EFI_PAGE_SIZE#endif +static efi_status_t get_memory_map (efi_system_table_t *sys_table_arg, +efi_memory_desc_t **map, +unsigned long *map_size, +unsigned long *desc_size, +u32 *desc_ver,unsigned long *key_ptr) +{ +efi_status_t status; + +/* +* Call get_memory_map() with 0 size to retrieve the size of the +* required allocation. +*/ + *map_size =0 ; + status =efi_call_early (get_memory_map, map_size,NULL , + key_ptr, desc_size, desc_ver); +if (status !=EFI_BUFFER_TOO_SMALL ) +return EFI_LOAD_ERROR ; + +/* +* Add an additional efi_memory_desc_t to map_size because we're doing +* an allocation which may be in a new descriptor region. Then double it +* to give us some scratch space to prepare the input virtmap to give +* to SetVirtualAddressMap(). Note that this is EFI_LOADER_DATA memory, +* and the kernel memblock_reserve()'s only the size of the actual +* memory map, so the scratch space is freed again automatically. +*/ + *map_size += *desc_size; + status = efi_call_early(allocate_pool, EFI_LOADER_DATA,
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 207
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+ *map_size * 2, (void **)map); +if (status !=EFI_SUCCESS ) +return status; + + status =efi_call_early (get_memory_map, map_size, *map, + key_ptr, desc_size, desc_ver); +if (status !=EFI_SUCCESS ) +efi_call_early (free_pool, *map); +return status; +}
We've now got two (slightly different) versions of this function. Is there any way we could make do with just one?
Quoted 39 lines
drivers/firmware/efi/libstub/fdt.c +39
-0+/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000 + +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M ) + efi_virt_base =round_up (efi_virt_base,SZ_2M );
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 257
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+ + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +} +
fdt.c is starting to become a dumping ground for arm*-specific stuff :-(
Is there no general solution for sharing code between arm and aarch64 in the kernel so we don't have to stick things like this in drivers/firmware/efi/?
Signature · 1 line
Matt Fleming, Intel Open Source Technology Center
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 33 lines · Matt Fleming
Quoted 33 lines
drivers/firmware/efi/libstub/fdt.c +33
-0+static efi_status_t get_memory_map (efi_system_table_t *sys_table_arg, +efi_memory_desc_t **map, +unsigned long *map_size, +unsigned long *desc_size, +u32 *desc_ver,unsigned long *key_ptr) +{ +efi_status_t status; + +/* +* Call get_memory_map() with 0 size to retrieve the size of the +* required allocation. +*/ + *map_size =0 ; + status =efi_call_early (get_memory_map, map_size,NULL , + key_ptr, desc_size, desc_ver); +if (status !=EFI_BUFFER_TOO_SMALL ) +return EFI_LOAD_ERROR ; + +/* +* Add an additional efi_memory_desc_t to map_size because we're doing +* an allocation which may be in a new descriptor region. Then double it +* to give us some scratch space to prepare the input virtmap to give +* to SetVirtualAddressMap(). Note that this is EFI_LOADER_DATA memory, +* and the kernel memblock_reserve()'s only the size of the actual +* memory map, so the scratch space is freed again automatically. +*/ + *map_size += *desc_size; + status =efi_call_early (allocate_pool,EFI_LOADER_DATA , + *map_size *2 , (void **)map); +if (status !=EFI_SUCCESS ) +return status; + + status = efi_call_early(get_memory_map, map_size, *map,
Quoted 8 lines
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 207
Quoted 5 lines
drivers/firmware/efi/libstub/fdt.c +5
-0+ key_ptr, desc_size, desc_ver); +if (status !=EFI_SUCCESS ) +efi_call_early (free_pool, *map); +return status; +}We've now got two (slightly different) versions of this function. Is there any way we could make do with just one?
I think all we really need above what efi_get_memory_map() provides is the scratch space. Would we care about temporarily wasting a little bit of EFI_LOADER_DATA on all platforms, or could we just swap the function body in efi-stub-helper.c for Ard's version above?
(I would guess memory maps with <= 32 entries are uncommon anyway, so the existing version would already make the bootservice call twice.)
Quoted 43 lines
Quoted 43 lines
drivers/firmware/efi/libstub/fdt.c +43
-0+/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000 + +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M ) + efi_virt_base =round_up (efi_virt_base,SZ_2M ); + + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; +
Quoted 8 lines
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 257
Quoted 6 lines
drivers/firmware/efi/libstub/fdt.c +6
-0+memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +} +
fdt.cis starting to become a dumping ground for arm*-specific stuff :-(
Mmm, not optimal.
That said, the only arm*-specific things about this particular function are the page sizes. Should this move to efi-stub-helper.c with EFI_RT_VIRTUAL_BASE moved to arch/<x>/include/asm/efi.h and joined by EFI_RT_VIRTUAL_BASE_ALIGN and EFI_RT_VIRTUAL_REGION_ALIGN?
Quoted 3 lines
Is there no general solution for sharing code between arm and aarch64 in the kernel so we don't have to stick things like this in
drivers/firmware/efi/?
Not currently.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 9 lines · Leif Lindholm
On Mon, Jan 05, 2015 at 04:54:02PM +0000, Matt Fleming wrote:
I think all we really need above what
efi_get_memory_map()provides is the scratch space. Would we care about temporarily wasting a little bit ofEFI_LOADER_DATAon all platforms, or could we just swap the function body inefi-stub-helper.cfor Ard's version above?(I would guess memory maps with <= 32 entries are uncommon anyway, so the existing version would already make the bootservice call twice.)
I've no concerns about using the additional scratch space.
[...]
Quoted 5 lines
Mmm, not optimal.
That said, the only arm*-specific things about this particular function are the page sizes. Should this move toefi-stub-helper.cwithEFI_RT_VIRTUAL_BASEmoved to arch/<x>/include/asm/efi.h and joined byEFI_RT_VIRTUAL_BASE_ALIGNandEFI_RT_VIRTUAL_REGION_ALIGN?
Yeah, that would be an improvement. It's possible we could reuse some of this code for x86's EFI virtual mapping code that Borislav wrote (maybe).
Signature · 1 line
Matt Fleming, Intel Open Source Technology Center
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
In reply to Matt FlemingQuoted 29 lines · Matt Fleming
Quoted 22 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)[...]
Quoted 3 lines
arch/arm64/include/asm/efi.h +0
-0@@ -45,5 +53,9 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__)
Quoted 7 lines
arch/arm64/include/asm/efi.h extern void efi_idmap_init(void); · line 56
Quoted 2 lines
arch/arm64/include/asm/efi.h +1
-0#define EFI_ALLOC_ALIGN SZ_64K +#define EFI_VIRTMAP EFI_ARCH_1Any chance of documenting what
EFI_VIRTMAPmeans for posterity and why you want to use one of the EFI arch config bits? How is this different fromEFI_RUNTIME_SERVICES?
Will do. It means the virtmap page tables have been set up, based on the virtual-to-physical mapping that the stub inserted into the memory map.
This becomes a prereq for enabling the runtime services.
Quoted 46 lines
Take a look at
EFI_OLD_MEMMAPinarch/x86/include/asm/efi.hfor a crackingly well documented example from Borislav.[...]
Quoted 41 lines
drivers/firmware/efi/libstub/fdt.c +33
-0@@ -167,6 +167,94 @@ fdt_set_fail:#define EFI_FDT_ALIGN EFI_PAGE_SIZE#endif +static efi_status_t get_memory_map (efi_system_table_t *sys_table_arg, +efi_memory_desc_t **map, +unsigned long *map_size, +unsigned long *desc_size, +u32 *desc_ver,unsigned long *key_ptr) +{ +efi_status_t status; + +/* +* Call get_memory_map() with 0 size to retrieve the size of the +* required allocation. +*/ + *map_size =0 ; + status =efi_call_early (get_memory_map, map_size,NULL , + key_ptr, desc_size, desc_ver); +if (status !=EFI_BUFFER_TOO_SMALL ) +return EFI_LOAD_ERROR ; + +/* +* Add an additional efi_memory_desc_t to map_size because we're doing +* an allocation which may be in a new descriptor region. Then double it +* to give us some scratch space to prepare the input virtmap to give +* to SetVirtualAddressMap(). Note that this is EFI_LOADER_DATA memory, +* and the kernel memblock_reserve()'s only the size of the actual +* memory map, so the scratch space is freed again automatically. +*/ + *map_size += *desc_size; + status =efi_call_early (allocate_pool,EFI_LOADER_DATA , + *map_size *2 , (void **)map); +if (status !=EFI_SUCCESS ) +return status; + + status = efi_call_early(get_memory_map, map_size, *map,
Quoted 9 lines
drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 207
Quoted 5 lines
drivers/firmware/efi/libstub/fdt.c +5
-0+ key_ptr, desc_size, desc_ver); +if (status !=EFI_SUCCESS ) +efi_call_early (free_pool, *map); +return status; +}We've now got two (slightly different) versions of this function. Is there any way we could make do with just one?
I have seen some ludicrously large memory maps on some of my x86 boxes, so I was reluctant to just double the size for all users. I am happy to make this the default implementation, but I am not sure if x86 frees the second half implicitly as arm does.
Quoted 52 lines
Quoted 39 lines
drivers/firmware/efi/libstub/fdt.c +39
-0+/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000 + +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M ) + efi_virt_base =round_up (efi_virt_base,SZ_2M );drivers/firmware/efi/libstub/fdt.c fdt_set_fail: · line 257
Quoted 10 lines
drivers/firmware/efi/libstub/fdt.c +10
-0+ + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +} +
fdt.cis starting to become a dumping ground for arm*-specific stuff :-(
Quoted 4 lines
Is there no general solution for sharing code between arm and aarch64 in the kernel so we don't have to stick things like this in
drivers/firmware/efi/?
I will put these functions in arm-stub.c instead.
Signature · 1 line
Ard.
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
In reply to Ard BiesheuvelQuoted 36 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)arch/arm64/include/asm/efi.h +2
-0@@ -7,28 +7,36 @@#ifdef CONFIG_EFI extern void efi_init (void );extern void efi_idmap_init (void ); +extern void efi_virtmap_init (void );#else #define efi_init ()#define efi_idmap_init () +#define efi_virtmap_init
arch/arm64/include/asm/efi.h line 22
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2#endif #define efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ efi_status_t __s; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \
Nitpick: adding comment to otherwise untouched source line.
Quoted 5 lines
arch/arm64/include/asm/efi.h +3
-0+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \ __s =__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \
arch/arm64/include/asm/efi.h line 35
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2__s; \ })#define __efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \
Same nitpick.
Quoted 143 lines
arch/arm64/include/asm/efi.h +7
-0+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ })@@ -45,5 +53,9 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__)#define EFI_ALLOC_ALIGN SZ_64K +#define EFI_VIRTMAP EFI_ARCH_1 + +void efi_virtmap_load (void ); +void efi_virtmap_unload (void );#endif /* _ASM_EFI_H */ arch/arm64/kernel/efi.c +39
-30@@ -11,25 +11,30 @@* */ +#include <linux/atomic.h> #include <linux/dmi.h> #include <linux/efi.h> #include <linux/export.h> #include <linux/memblock.h> +#include <linux/mm_types.h> #include <linux/bootmem.h> #include <linux/of.h> #include <linux/of_fdt.h> +#include <linux/rbtree.h> +#include <linux/rwsem.h> #include <linux/sched.h> #include <linux/slab.h> +#include <linux/spinlock.h> #include <asm/cacheflush.h> #include <asm/efi.h> #include <asm/tlbflush.h> #include <asm/mmu_context.h> +#include <asm/mmu.h> +#include <asm/pgtable.h> struct efi_memory_map memmap; -static efi_runtime_services_t *runtime; -static u64 efi_system_table;static int uefi_debug__initdata ;@@ -69,9 +74,33 @@ static void __init efi_setup_idmap(void) } } +/* +* Translate a EFI virtual address into a physical address: this is necessary, +* as some data members of the EFI system table are virtually remapped after +* SetVirtualAddressMap() has been called. +*/ +static phys_addr_t efi_to_phys (unsigned long addr) +{ +efi_memory_desc_t *md; + +for_each_efi_memory_desc (&memmap, md) { +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; +if (md->virt_addr ==0 ) +/* no virtual mapping has been installed by the stub */ +break ; +if (md->virt_addr <= addr && + (addr - md->virt_addr) < (md->num_pages <<EFI_PAGE_SHIFT )) +return md->phys_addr + addr - md->virt_addr; + } +return addr; +} +static int __init uefi_init (void ) {efi_char16_t *c16; +void *config_tables; +u64 table_size;char vendor[100 ] ="unknown" ;int i, retval;@@ -99,7 +128,7 @@ static int __init uefi_init(void) efi.systab->hdr.revision & 0xffff);/* Show what we know for posterity */ - c16 =early_memremap (efi.systab->fw_vendor, + c16 =early_memremap (efi_to_phys (efi.systab->fw_vendor),sizeof (vendor));if (c16) {for (i =0 ; i < (int )sizeof (vendor) -1 && *c16; ++i)@@ -112,8 +141,14 @@ static int __init uefi_init(void) efi.systab->hdr.revision >>16 , efi.systab->hdr.revision & 0xffff, vendor); - retval =efi_config_init (NULL ); + table_size =sizeof (efi_config_table_64_t) * efi.systab->nr_tables; + config_tables =early_memremap (efi_to_phys (efi.systab->tables), + table_size); + + retval =efi_config_parse_tables (config_tables, + efi.systab->nr_tables,NULL ); +early_memunmap (config_tables, table_size); out:early_memunmap (efi.systab,sizeof (efi_system_table_t));return retval;@@ -328,51 +363,9 @@ void __init efi_idmap_init(void)efi_setup_idmap (); } -static int __init remap_region (efi_memory_desc_t *md,void **new) -{ -u64 paddr, vaddr, npages, size; - - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; - -if (is_normal_ram (md)) - vaddr = (__force u64 )ioremap_cache (paddr, size); -else - vaddr = (__force u64 )ioremap (paddr, size); - -if (!vaddr) { -pr_err ("Unable to remap 0x%llx pages @ %p\n" , - npages, (void *)paddr); -return 0 ; - } - -/* adjust for any rounding when EFI and system pagesize differs */ - md->virt_addr = vaddr + (md->phys_addr - paddr); - -if (uefi_debug) -pr_info (" EFI remap 0x%012llx => %p\n" , - md->phys_addr, (void *)md->virt_addr);
arch/arm64/kernel/efi.c void __init efi_idmap_init(void) · line 366
Quoted 10 lines
arch/arm64/kernel/efi.c +0
-10- -memcpy (*new, md, memmap.desc_size); - *new += memmap.desc_size; - -return 1 ; -} - -/* -* Switch UEFI from an identity map to a kernel virtual map -*/
No function description at all?
Arguably this function could change name now as well, since UEFI will already be in virtual mode. arm64_enable_runtime_map()?
Quoted 182 lines
arch/arm64/kernel/efi.c +81
-63static int __init arm64_enter_virtual_mode (void ) { -efi_memory_desc_t *md; -phys_addr_t virtmap_phys; -void *virtmap, *virt_md; -efi_status_t status;u64 mapsize; -int count =0 ; -unsigned long flags;if (!efi_enabled (EFI_BOOT )) {pr_info ("EFI services will not be available.\n" );@@ -395,79 +388,28 @@ static int __init arm64_enter_virtual_mode(void) efi.memmap = &memmap; -/* Map the runtime regions */ - virtmap =kmalloc (mapsize,GFP_KERNEL ); -if (!virtmap) { -pr_err ("Failed to allocate EFI virtual memmap\n" ); -return -1 ; - } - virtmap_phys =virt_to_phys (virtmap); - virt_md = virtmap; - -for_each_efi_memory_desc (&memmap, md) { -if (!(md->attribute &EFI_MEMORY_RUNTIME )) -continue ; -if (!remap_region (md, &virt_md)) - goto err_unmap; - ++count; - } - - efi.systab = (__force void *)efi_lookup_mapped_addr (efi_system_table); + efi.systab = (__force void *)ioremap_cache (efi_system_table, +sizeof (efi_system_table_t));if (!efi.systab) { -/* -* If we have no virtual mapping for the System Table at this -* point, the memory map doesn't cover the physical offset where -* it resides. This means the System Table will be inaccessible -* to Runtime Services themselves once the virtual mapping is -* installed. -*/ -pr_err ("Failed to remap EFI System Table -- buggy firmware?\n" ); - goto err_unmap; +pr_err ("Failed to remap EFI System Table\n" ); +return -1 ; }set_bit (EFI_SYSTEM_TABLES , &efi.flags); -local_irq_save (flags); -cpu_switch_mm (idmap_pg_dir, &init_mm); - -/* Call SetVirtualAddressMap with the physical address of the map */ - runtime = efi.systab->runtime; - efi.set_virtual_address_map = runtime->set_virtual_address_map; - - status = efi.set_virtual_address_map (count * memmap.desc_size, - memmap.desc_size, - memmap.desc_version, - (efi_memory_desc_t *)virtmap_phys); -cpu_set_reserved_ttbr0 (); -flush_tlb_all (); -local_irq_restore (flags); - -kfree (virtmap); -free_boot_services (); -if (status !=EFI_SUCCESS ) { -pr_err ("Failed to set EFI virtual address map! [%lx]\n" , - status); +if (!efi_enabled (EFI_VIRTMAP )) { +pr_err ("No UEFI virtual mapping was installed -- runtime services will not be available\n" );return -1 ; }/* Set up runtime services function pointers */ - runtime = efi.systab->runtime;efi_native_runtime_setup ();set_bit (EFI_RUNTIME_SERVICES , &efi.flags); efi.runtime_version = efi.systab->hdr.revision;return 0 ; - -err_unmap: -/* unmap all mappings that succeeded: there are 'count' of those */ -for (virt_md = virtmap; count--; virt_md += memmap.desc_size) { - md = virt_md; -iounmap ((__force void __iomem *)md->virt_addr); - } -kfree (virtmap); -return -1 ; }early_initcall (arm64_enter_virtual_mode);@@ -484,3 +426,78 @@ static int __init arm64_dmi_init(void)return 0 ; }core_initcall (arm64_dmi_init); + +static pgd_t efi_pgd[PTRS_PER_PGD] __page_aligned_bss; + +static struct mm_struct efi_mm = { + .mm_rb =RB_ROOT , + .pgd = efi_pgd, + .mm_users =ATOMIC_INIT (2 ), + .mm_count =ATOMIC_INIT (1 ), + .mmap_sem =__RWSEM_INITIALIZER (efi_mm.mmap_sem), + .page_table_lock =__SPIN_LOCK_UNLOCKED (efi_mm.page_table_lock), + .mmlist =LIST_HEAD_INIT (efi_mm.mmlist), +INIT_MM_CONTEXT (efi_mm) +}; + +static void efi_set_pgd (struct mm_struct *mm) +{ +cpu_switch_mm (mm->pgd, mm); +flush_tlb_all (); +if (icache_is_aivivt ()) +__flush_icache_all (); +} + +void efi_virtmap_load (void ) +{ +WARN_ON (preemptible ()); +efi_set_pgd (&efi_mm); +} + +void efi_virtmap_unload (void ) +{ +efi_set_pgd (current->active_mm); +} + +void __init efi_virtmap_init (void ) +{ +efi_memory_desc_t *md; + +if (!efi_enabled (EFI_BOOT )) +return ; + +for_each_efi_memory_desc (&memmap, md) { +u64 paddr, npages, size; +pgprot_t prot; + +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; +if (WARN (md->virt_addr ==0 , +"UEFI virtual mapping incomplete or missing -- no entry found for 0x%llx\n" , + md->phys_addr)) +return ; + + paddr = md->phys_addr; + npages = md->num_pages; +memrange_efi_to_native (&paddr, &npages); + size = npages <<PAGE_SHIFT ; + +pr_info (" EFI remap 0x%012llx => %p\n" , + md->phys_addr, (void *)md->virt_addr); + +/* +* Only regions of type EFI_RUNTIME_SERVICES_CODE need to be +* executable, everything else can be mapped with the XN bits +* set. +*/ +if (!is_normal_ram (md)) + prot =__pgprot (PROT_DEVICE_nGnRE); +else if (md->type ==EFI_RUNTIME_SERVICES_CODE ) + prot =PAGE_KERNEL_EXEC ; +else + prot =PAGE_KERNEL ; + +create_pgd_mapping (&efi_mm, paddr, md->virt_addr, size, prot); + } +set_bit (EFI_VIRTMAP , &efi.flags); +}arch/arm64/kernel/setup.c +0
-0
arch/arm64/kernel/setup.c void __init setup_arch(char **cmdline_p) · line 405
Quoted 4 lines
arch/arm64/kernel/setup.c +1
-0@@ -402,6 +402,7 @@ void __init setup_arch(char **cmdline_p)request_standard_resources ();efi_idmap_init (); +efi_virtmap_init ();
Could these two be merged together into one function? Say efi_memmap_init()?
Quoted 178 lines
arch/arm64/kernel/setup.c +0
-0unflatten_device_tree ();drivers/firmware/efi/libstub/fdt.c +133
-4@@ -167,6 +167,94 @@ fdt_set_fail:#define EFI_FDT_ALIGN EFI_PAGE_SIZE#endif +static efi_status_t get_memory_map (efi_system_table_t *sys_table_arg, +efi_memory_desc_t **map, +unsigned long *map_size, +unsigned long *desc_size, +u32 *desc_ver,unsigned long *key_ptr) +{ +efi_status_t status; + +/* +* Call get_memory_map() with 0 size to retrieve the size of the +* required allocation. +*/ + *map_size =0 ; + status =efi_call_early (get_memory_map, map_size,NULL , + key_ptr, desc_size, desc_ver); +if (status !=EFI_BUFFER_TOO_SMALL ) +return EFI_LOAD_ERROR ; + +/* +* Add an additional efi_memory_desc_t to map_size because we're doing +* an allocation which may be in a new descriptor region. Then double it +* to give us some scratch space to prepare the input virtmap to give +* to SetVirtualAddressMap(). Note that this is EFI_LOADER_DATA memory, +* and the kernel memblock_reserve()'s only the size of the actual +* memory map, so the scratch space is freed again automatically. +*/ + *map_size += *desc_size; + status =efi_call_early (allocate_pool,EFI_LOADER_DATA , + *map_size *2 , (void **)map); +if (status !=EFI_SUCCESS ) +return status; + + status =efi_call_early (get_memory_map, map_size, *map, + key_ptr, desc_size, desc_ver); +if (status !=EFI_SUCCESS ) +efi_call_early (free_pool, *map); +return status; +} + +/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000 + +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M ) + efi_virt_base =round_up (efi_virt_base,SZ_2M ); + + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +} +/* * Allocate memory for a new FDT, then add EFI, commandline, and * initrd related fields to the FDT. This routine increases the @@ -196,6 +284,7 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table,efi_memory_desc_t *memory_map;unsigned long new_fdt_size;efi_status_t status; +int runtime_entry_count =0 ;/* * Estimate size of new FDT, and allocate memory for it. We @@ -216,8 +305,8 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table,* we can get the memory map key needed for * exit_boot_services(). */ - status =efi_get_memory_map (sys_table, &memory_map, &map_size, - &desc_size, &desc_ver, &mmap_key); + status =get_memory_map (sys_table, &memory_map, &map_size, + &desc_size, &desc_ver, &mmap_key);if (status !=EFI_SUCCESS ) goto fail_free_new_fdt;@@ -248,12 +337,52 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, } } +/* +* Update the memory map with virtual addresses. The function will also +* populate the spare second half of the memory_map allocation with +* copies of just the EFI_MEMORY_RUNTIME entries so that we can pass it +* straight into SetVirtualAddressMap() +*/ +update_memory_map (memory_map, map_size, desc_size, + &runtime_entry_count); + +pr_efi (sys_table, +"Exiting boot services and installing virtual address map...\n" ); +/* Now we are ready to exit_boot_services.*/ status = sys_table->boottime->exit_boot_services (handle, mmap_key); +if (status ==EFI_SUCCESS ) { +efi_set_virtual_address_map_t *svam; -if (status ==EFI_SUCCESS ) -return status; +/* Install the new virtual address map */ + svam = sys_table->runtime->set_virtual_address_map; + status =svam (runtime_entry_count * desc_size, desc_size, + desc_ver, (void *)memory_map + map_size); + +/* +* We are beyond the point of no return here, so if the call to +* SetVirtualAddressMap() failed, we need to signal that to the +* incoming kernel but proceed normally otherwise. +*/ +if (status !=EFI_SUCCESS ) { +int l; + +/* +* Set the virtual address field of all +* EFI_MEMORY_RUNTIME entries to 0. This will signal +* the incoming kernel that no virtual translation has +* been installed. +*/ +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *p = (void *)memory_map + l; + +if (p->attribute &EFI_MEMORY_RUNTIME ) + p->virt_addr =0 ; + } + } +return EFI_SUCCESS ; + }pr_efi_err (sys_table,"Exit boot services failed.\n" );Signature · 1 line
1.8.3.2
Apart from this, and other comments in the thread, looks good.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 66 lines · Leif Lindholm
Quoted 36 lines · Ard Biesheuvel
In order to support kexec, the kernel needs to be able to deal with the state of the UEFI firmware after
SetVirtualAddressMap()has been called. To avoid having separate code paths for non-kexec and kexec, let's move the call toSetVirtualAddressMap()to the stub: this will guarantee us that it will only be called once (since the stub is not executed during kexec), and ensures that the UEFI state is identical between kexec and normal boot.This implies that the layout of the virtual mapping needs to be created by the stub as well. All regions are rounded up to a naturally aligned multiple of 64 KB (for compatibility with 64k pages kernels) and recorded in the UEFI memory map. The kernel proper reads those values and installs the mappings in a dedicated set of page tables that are swapped in during UEFI Runtime Services calls.
Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 20 +++- arch/arm64/kernel/efi.c | 223 ++++++++++++++++++++----------------- arch/arm64/kernel/setup.c | 1 + drivers/firmware/efi/libstub/fdt.c | 137 ++++++++++++++++++++++- 4 files changed, 270 insertions(+), 111 deletions(-)arch/arm64/include/asm/efi.h +2
-0@@ -7,28 +7,36 @@#ifdef CONFIG_EFI extern void efi_init (void );extern void efi_idmap_init (void ); +extern void efi_virtmap_init (void );#else #define efi_init ()#define efi_idmap_init () +#define efi_virtmap_initarch/arm64/include/asm/efi.h line 22
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2#endif #define efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ efi_status_t __s; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \Nitpick: adding comment to otherwise untouched source line.
Quoted 5 lines
arch/arm64/include/asm/efi.h +3
-0+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \ __s =__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \arch/arm64/include/asm/efi.h line 35
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2__s; \ })#define __efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \
Quoted 2 lines
Same nitpick.
Is there anything wrong with that?
Would you prefer the comment to be on a separate line?
Quoted 147 lines
Quoted 147 lines
arch/arm64/include/asm/efi.h +7
-0+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ })@@ -45,5 +53,9 @@ extern void efi_idmap_init(void);#define efi_call_early (f, ...) sys_table_arg->boottime->f(__VA_ARGS__)#define EFI_ALLOC_ALIGN SZ_64K +#define EFI_VIRTMAP EFI_ARCH_1 + +void efi_virtmap_load (void ); +void efi_virtmap_unload (void );#endif /* _ASM_EFI_H */ arch/arm64/kernel/efi.c +39
-34@@ -11,25 +11,30 @@* */ +#include <linux/atomic.h> #include <linux/dmi.h> #include <linux/efi.h> #include <linux/export.h> #include <linux/memblock.h> +#include <linux/mm_types.h> #include <linux/bootmem.h> #include <linux/of.h> #include <linux/of_fdt.h> +#include <linux/rbtree.h> +#include <linux/rwsem.h> #include <linux/sched.h> #include <linux/slab.h> +#include <linux/spinlock.h> #include <asm/cacheflush.h> #include <asm/efi.h> #include <asm/tlbflush.h> #include <asm/mmu_context.h> +#include <asm/mmu.h> +#include <asm/pgtable.h> struct efi_memory_map memmap; -static efi_runtime_services_t *runtime; -static u64 efi_system_table;static int uefi_debug__initdata ;@@ -69,9 +74,33 @@ static void __init efi_setup_idmap(void) } } +/* +* Translate a EFI virtual address into a physical address: this is necessary, +* as some data members of the EFI system table are virtually remapped after +* SetVirtualAddressMap() has been called. +*/ +static phys_addr_t efi_to_phys (unsigned long addr) +{ +efi_memory_desc_t *md; + +for_each_efi_memory_desc (&memmap, md) { +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; +if (md->virt_addr ==0 ) +/* no virtual mapping has been installed by the stub */ +break ; +if (md->virt_addr <= addr && + (addr - md->virt_addr) < (md->num_pages <<EFI_PAGE_SHIFT )) +return md->phys_addr + addr - md->virt_addr; + } +return addr; +} +static int __init uefi_init (void ) {efi_char16_t *c16; +void *config_tables; +u64 table_size;char vendor[100 ] ="unknown" ;int i, retval;@@ -99,7 +128,7 @@ static int __init uefi_init(void) efi.systab->hdr.revision & 0xffff);/* Show what we know for posterity */ - c16 =early_memremap (efi.systab->fw_vendor, + c16 =early_memremap (efi_to_phys (efi.systab->fw_vendor),sizeof (vendor));if (c16) {for (i =0 ; i < (int )sizeof (vendor) -1 && *c16; ++i)@@ -112,8 +141,14 @@ static int __init uefi_init(void) efi.systab->hdr.revision >>16 , efi.systab->hdr.revision & 0xffff, vendor); - retval =efi_config_init (NULL ); + table_size =sizeof (efi_config_table_64_t) * efi.systab->nr_tables; + config_tables =early_memremap (efi_to_phys (efi.systab->tables), + table_size); + + retval =efi_config_parse_tables (config_tables, + efi.systab->nr_tables,NULL ); +early_memunmap (config_tables, table_size); out:early_memunmap (efi.systab,sizeof (efi_system_table_t));return retval;@@ -328,51 +363,9 @@ void __init efi_idmap_init(void)efi_setup_idmap (); } -static int __init remap_region (efi_memory_desc_t *md,void **new) -{ -u64 paddr, vaddr, npages, size; - - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; - -if (is_normal_ram (md)) - vaddr = (__force u64 )ioremap_cache (paddr, size); -else - vaddr = (__force u64 )ioremap (paddr, size); - -if (!vaddr) { -pr_err ("Unable to remap 0x%llx pages @ %p\n" , - npages, (void *)paddr); -return 0 ; - } - -/* adjust for any rounding when EFI and system pagesize differs */ - md->virt_addr = vaddr + (md->phys_addr - paddr); - -if (uefi_debug) -pr_info (" EFI remap 0x%012llx => %p\n" , - md->phys_addr, (void *)md->virt_addr); - -memcpy (*new, md, memmap.desc_size); - *new += memmap.desc_size; -
Quoted 8 lines
arch/arm64/kernel/efi.c void __init efi_idmap_init(void) · line 366
Quoted 6 lines
arch/arm64/kernel/efi.c +0
-6-return 1 ; -} - -/* -* Switch UEFI from an identity map to a kernel virtual map -*/ No function description at all?
Seems I was a bit lazy there.
Quoted 3 lines
Arguably this function could change name now as well, since UEFI will already be in virtual mode.
arm64_enable_runtime_map()?
OK
Quoted 184 lines
Quoted 184 lines
arch/arm64/kernel/efi.c +81
-63static int __init arm64_enter_virtual_mode (void ) { -efi_memory_desc_t *md; -phys_addr_t virtmap_phys; -void *virtmap, *virt_md; -efi_status_t status;u64 mapsize; -int count =0 ; -unsigned long flags;if (!efi_enabled (EFI_BOOT )) {pr_info ("EFI services will not be available.\n" );@@ -395,79 +388,28 @@ static int __init arm64_enter_virtual_mode(void) efi.memmap = &memmap; -/* Map the runtime regions */ - virtmap =kmalloc (mapsize,GFP_KERNEL ); -if (!virtmap) { -pr_err ("Failed to allocate EFI virtual memmap\n" ); -return -1 ; - } - virtmap_phys =virt_to_phys (virtmap); - virt_md = virtmap; - -for_each_efi_memory_desc (&memmap, md) { -if (!(md->attribute &EFI_MEMORY_RUNTIME )) -continue ; -if (!remap_region (md, &virt_md)) - goto err_unmap; - ++count; - } - - efi.systab = (__force void *)efi_lookup_mapped_addr (efi_system_table); + efi.systab = (__force void *)ioremap_cache (efi_system_table, +sizeof (efi_system_table_t));if (!efi.systab) { -/* -* If we have no virtual mapping for the System Table at this -* point, the memory map doesn't cover the physical offset where -* it resides. This means the System Table will be inaccessible -* to Runtime Services themselves once the virtual mapping is -* installed. -*/ -pr_err ("Failed to remap EFI System Table -- buggy firmware?\n" ); - goto err_unmap; +pr_err ("Failed to remap EFI System Table\n" ); +return -1 ; }set_bit (EFI_SYSTEM_TABLES , &efi.flags); -local_irq_save (flags); -cpu_switch_mm (idmap_pg_dir, &init_mm); - -/* Call SetVirtualAddressMap with the physical address of the map */ - runtime = efi.systab->runtime; - efi.set_virtual_address_map = runtime->set_virtual_address_map; - - status = efi.set_virtual_address_map (count * memmap.desc_size, - memmap.desc_size, - memmap.desc_version, - (efi_memory_desc_t *)virtmap_phys); -cpu_set_reserved_ttbr0 (); -flush_tlb_all (); -local_irq_restore (flags); - -kfree (virtmap); -free_boot_services (); -if (status !=EFI_SUCCESS ) { -pr_err ("Failed to set EFI virtual address map! [%lx]\n" , - status); +if (!efi_enabled (EFI_VIRTMAP )) { +pr_err ("No UEFI virtual mapping was installed -- runtime services will not be available\n" );return -1 ; }/* Set up runtime services function pointers */ - runtime = efi.systab->runtime;efi_native_runtime_setup ();set_bit (EFI_RUNTIME_SERVICES , &efi.flags); efi.runtime_version = efi.systab->hdr.revision;return 0 ; - -err_unmap: -/* unmap all mappings that succeeded: there are 'count' of those */ -for (virt_md = virtmap; count--; virt_md += memmap.desc_size) { - md = virt_md; -iounmap ((__force void __iomem *)md->virt_addr); - } -kfree (virtmap); -return -1 ; }early_initcall (arm64_enter_virtual_mode);@@ -484,3 +426,78 @@ static int __init arm64_dmi_init(void)return 0 ; }core_initcall (arm64_dmi_init); + +static pgd_t efi_pgd[PTRS_PER_PGD] __page_aligned_bss; + +static struct mm_struct efi_mm = { + .mm_rb =RB_ROOT , + .pgd = efi_pgd, + .mm_users =ATOMIC_INIT (2 ), + .mm_count =ATOMIC_INIT (1 ), + .mmap_sem =__RWSEM_INITIALIZER (efi_mm.mmap_sem), + .page_table_lock =__SPIN_LOCK_UNLOCKED (efi_mm.page_table_lock), + .mmlist =LIST_HEAD_INIT (efi_mm.mmlist), +INIT_MM_CONTEXT (efi_mm) +}; + +static void efi_set_pgd (struct mm_struct *mm) +{ +cpu_switch_mm (mm->pgd, mm); +flush_tlb_all (); +if (icache_is_aivivt ()) +__flush_icache_all (); +} + +void efi_virtmap_load (void ) +{ +WARN_ON (preemptible ()); +efi_set_pgd (&efi_mm); +} + +void efi_virtmap_unload (void ) +{ +efi_set_pgd (current->active_mm); +} + +void __init efi_virtmap_init (void ) +{ +efi_memory_desc_t *md; + +if (!efi_enabled (EFI_BOOT )) +return ; + +for_each_efi_memory_desc (&memmap, md) { +u64 paddr, npages, size; +pgprot_t prot; + +if (!(md->attribute &EFI_MEMORY_RUNTIME )) +continue ; +if (WARN (md->virt_addr ==0 , +"UEFI virtual mapping incomplete or missing -- no entry found for 0x%llx\n" , + md->phys_addr)) +return ; + + paddr = md->phys_addr; + npages = md->num_pages; +memrange_efi_to_native (&paddr, &npages); + size = npages <<PAGE_SHIFT ; + +pr_info (" EFI remap 0x%012llx => %p\n" , + md->phys_addr, (void *)md->virt_addr); + +/* +* Only regions of type EFI_RUNTIME_SERVICES_CODE need to be +* executable, everything else can be mapped with the XN bits +* set. +*/ +if (!is_normal_ram (md)) + prot =__pgprot (PROT_DEVICE_nGnRE); +else if (md->type ==EFI_RUNTIME_SERVICES_CODE ) + prot =PAGE_KERNEL_EXEC ; +else + prot =PAGE_KERNEL ; + +create_pgd_mapping (&efi_mm, paddr, md->virt_addr, size, prot); + } +set_bit (EFI_VIRTMAP , &efi.flags); +}arch/arm64/kernel/setup.c +0
-0@@ -402,6 +402,7 @@ void __init setup_arch(char **cmdline_p)request_standard_resources ();
Quoted 6 lines
arch/arm64/kernel/setup.c void __init setup_arch(char **cmdline_p) · line 405
Quoted 2 lines
arch/arm64/kernel/setup.c +1
-0efi_idmap_init (); +efi_virtmap_init ();Could these two be merged together into one function? Say
efi_memmap_init()?
Well, I decided to do it like this because efi_idmap_init() gets removed in its entirety (including this invocation) in a subsequent patch.
Quoted 184 lines
Quoted 177 lines
arch/arm64/kernel/setup.c +0
-0unflatten_device_tree ();drivers/firmware/efi/libstub/fdt.c +133
-5@@ -167,6 +167,94 @@ fdt_set_fail:#define EFI_FDT_ALIGN EFI_PAGE_SIZE#endif +static efi_status_t get_memory_map (efi_system_table_t *sys_table_arg, +efi_memory_desc_t **map, +unsigned long *map_size, +unsigned long *desc_size, +u32 *desc_ver,unsigned long *key_ptr) +{ +efi_status_t status; + +/* +* Call get_memory_map() with 0 size to retrieve the size of the +* required allocation. +*/ + *map_size =0 ; + status =efi_call_early (get_memory_map, map_size,NULL , + key_ptr, desc_size, desc_ver); +if (status !=EFI_BUFFER_TOO_SMALL ) +return EFI_LOAD_ERROR ; + +/* +* Add an additional efi_memory_desc_t to map_size because we're doing +* an allocation which may be in a new descriptor region. Then double it +* to give us some scratch space to prepare the input virtmap to give +* to SetVirtualAddressMap(). Note that this is EFI_LOADER_DATA memory, +* and the kernel memblock_reserve()'s only the size of the actual +* memory map, so the scratch space is freed again automatically. +*/ + *map_size += *desc_size; + status =efi_call_early (allocate_pool,EFI_LOADER_DATA , + *map_size *2 , (void **)map); +if (status !=EFI_SUCCESS ) +return status; + + status =efi_call_early (get_memory_map, map_size, *map, + key_ptr, desc_size, desc_ver); +if (status !=EFI_SUCCESS ) +efi_call_early (free_pool, *map); +return status; +} + +/* +* This is the base address at which to start allocating virtual memory ranges +* for UEFI Runtime Services. This is a userland range so that we can use any +* allocation we choose, and eliminate the risk of a conflict after kexec. +*/ +#define EFI_RT_VIRTUAL_BASE 0x40000000 + +static void update_memory_map (efi_memory_desc_t *memory_map, +unsigned long map_size,unsigned long desc_size, +int *count) +{ +u64 efi_virt_base =EFI_RT_VIRTUAL_BASE ; +efi_memory_desc_t *out = (void *)memory_map + map_size; +int l; + +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *in = (void *)memory_map + l; +u64 paddr, size; + +if (!(in->attribute &EFI_MEMORY_RUNTIME )) +continue ; + +/* +* Make the mapping compatible with 64k pages: this allows +* a 4k page size kernel to kexec a 64k page size kernel and +* vice versa. +*/ + paddr =round_down (in->phys_addr,SZ_64K ); + size =round_up (in->num_pages *EFI_PAGE_SIZE + + in->phys_addr - paddr,SZ_64K ); + +/* +* Avoid wasting memory on PTEs by choosing a virtual base that +* is compatible with section mappings if this region has the +* appropriate size and physical alignment. (Sections are 2 MB +* on 4k granule kernels) +*/ +if (IS_ALIGNED (in->phys_addr,SZ_2M ) && size >=SZ_2M ) + efi_virt_base =round_up (efi_virt_base,SZ_2M ); + + in->virt_addr = efi_virt_base + in->phys_addr - paddr; + efi_virt_base += size; + +memcpy (out, in, desc_size); + out = (void *)out + desc_size; + ++*count; + } +} +/* * Allocate memory for a new FDT, then add EFI, commandline, and * initrd related fields to the FDT. This routine increases the @@ -196,6 +284,7 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table,efi_memory_desc_t *memory_map;unsigned long new_fdt_size;efi_status_t status; +int runtime_entry_count =0 ;/* * Estimate size of new FDT, and allocate memory for it. We @@ -216,8 +305,8 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table,* we can get the memory map key needed for * exit_boot_services(). */ - status =efi_get_memory_map (sys_table, &memory_map, &map_size, - &desc_size, &desc_ver, &mmap_key); + status =get_memory_map (sys_table, &memory_map, &map_size, + &desc_size, &desc_ver, &mmap_key);if (status !=EFI_SUCCESS ) goto fail_free_new_fdt;@@ -248,12 +337,52 @@ efi_status_t allocate_new_fdt_and_exit_boot(efi_system_table_t *sys_table, } } +/* +* Update the memory map with virtual addresses. The function will also +* populate the spare second half of the memory_map allocation with +* copies of just the EFI_MEMORY_RUNTIME entries so that we can pass it +* straight into SetVirtualAddressMap() +*/ +update_memory_map (memory_map, map_size, desc_size, + &runtime_entry_count); + +pr_efi (sys_table, +"Exiting boot services and installing virtual address map...\n" ); +/* Now we are ready to exit_boot_services.*/ status = sys_table->boottime->exit_boot_services (handle, mmap_key); +if (status ==EFI_SUCCESS ) { +efi_set_virtual_address_map_t *svam; -if (status ==EFI_SUCCESS ) -return status; +/* Install the new virtual address map */ + svam = sys_table->runtime->set_virtual_address_map; + status =svam (runtime_entry_count * desc_size, desc_size, + desc_ver, (void *)memory_map + map_size); + +/* +* We are beyond the point of no return here, so if the call to +* SetVirtualAddressMap() failed, we need to signal that to the +* incoming kernel but proceed normally otherwise. +*/ +if (status !=EFI_SUCCESS ) { +int l; + +/* +* Set the virtual address field of all +* EFI_MEMORY_RUNTIME entries to 0. This will signal +* the incoming kernel that no virtual translation has +* been installed. +*/ +for (l =0 ; l < map_size; l += desc_size) { +efi_memory_desc_t *p = (void *)memory_map + l; + +if (p->attribute &EFI_MEMORY_RUNTIME ) + p->virt_addr =0 ; + } + } +return EFI_SUCCESS ; + }pr_efi_err (sys_table,"Exit boot services failed.\n" ); --Quoted 1 line
1.8.3.2
Apart from this, and other comments in the thread, looks good.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 42 lines · Ard Biesheuvel
Quoted 42 lines
Quoted 13 lines
arch/arm64/include/asm/efi.h +2
-0@@ -7,28 +7,36 @@#ifdef CONFIG_EFI extern void efi_init (void );extern void efi_idmap_init (void ); +extern void efi_virtmap_init (void );#else #define efi_init ()#define efi_idmap_init () +#define efi_virtmap_initarch/arm64/include/asm/efi.h line 22
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2#endif #define efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ efi_status_t __s; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \Nitpick: adding comment to otherwise untouched source line.
Quoted 15 lines
arch/arm64/include/asm/efi.h +5
-2+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \ __s =__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ __s; \ })#define __efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \
Quoted 4 lines
Quoted 2 lines
Same nitpick.
Is there anything wrong with that?
I said nitpick.
My (very minor) objection is that a (very reasonable) comment is added to existing functionality by a patch that adds new functionality. It makes the git blame/praise output less clear.
Quoted 1 line
Would you prefer the comment to be on a separate line?
I would _prefer_ the comments to be a separate patch. But again, a nitpick.
Quoted 14 lines
Quoted 7 lines
Quoted 7 lines
arch/arm64/kernel/setup.c +0
-0@@ -402,6 +402,7 @@ void __init setup_arch(char **cmdline_p)request_standard_resources ();Quoted 6 lines
arch/arm64/kernel/setup.c void __init setup_arch(char **cmdline_p) · line 405
Quoted 2 lines
arch/arm64/kernel/setup.c +1
-0efi_idmap_init (); +efi_virtmap_init ();Could these two be merged together into one function? Say
efi_memmap_init()?
Quoted 3 lines
Well, I decided to do it like this because
efi_idmap_init()gets removed in its entirety (including this invocation) in a subsequent patch.
Ah yeah. I knew that yesterday. Ignore me. More coffee.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 50 lines · Leif Lindholm
Quoted 42 lines · Ard Biesheuvel
Quoted 42 lines
Quoted 13 lines
arch/arm64/include/asm/efi.h +2
-0@@ -7,28 +7,36 @@#ifdef CONFIG_EFI extern void efi_init (void );extern void efi_idmap_init (void ); +extern void efi_virtmap_init (void );#else #define efi_init ()#define efi_idmap_init () +#define efi_virtmap_initarch/arm64/include/asm/efi.h line 22
Quoted 10 lines
arch/arm64/include/asm/efi.h +2
-2#endif #define efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ efi_status_t __s; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \Nitpick: adding comment to otherwise untouched source line.
Quoted 15 lines
arch/arm64/include/asm/efi.h +5
-2+efi_virtmap_load (); \ + __f = efi.systab->runtime->f; \ __s =__f (__VA_ARGS__); \ +efi_virtmap_unload (); \kernel_neon_end (); \ __s; \ })#define __efi_call_virt (f, ...) \ ({ \ - efi_##f##_t *__f = efi.systab->runtime->f; \ + efi_##f##_t *__f; \ \ - kernel_neon_begin(); \ + kernel_neon_begin();/* disables preemption */ \Quoted 4 lines
Quoted 2 lines
Same nitpick.
Is there anything wrong with that?
I said nitpick.
Quoted 9 lines
My (very minor) objection is that a (very reasonable) comment is added to existing functionality by a patch that adds new functionality. It makes the git blame/praise output less clear.
Quoted 1 line
Would you prefer the comment to be on a separate line?
I would _prefer_ the comments to be a separate patch. But again, a nitpick.
Well, adding the comment is relevant to this patch, as we need to disable preemption now before switching to the new address space. In fact, it might be better even to drop the comment, and add an explicit (if redundant) preempt_disable/preempt_enable pair.
Quoted 22 lines
Quoted 14 lines
Quoted 7 lines
Quoted 7 lines
arch/arm64/kernel/setup.c +0
-0@@ -402,6 +402,7 @@ void __init setup_arch(char **cmdline_p)request_standard_resources ();Quoted 6 lines
arch/arm64/kernel/setup.c void __init setup_arch(char **cmdline_p) · line 405
Quoted 2 lines
arch/arm64/kernel/setup.c +1
-0efi_idmap_init (); +efi_virtmap_init ();Could these two be merged together into one function? Say
efi_memmap_init()?Quoted 3 lines
Well, I decided to do it like this because
efi_idmap_init()gets removed in its entirety (including this invocation) in a subsequent patch.Ah yeah. I knew that yesterday. Ignore me. More coffee.
/
Leif
PATCH v4 6/8 arm64/efi: move SetVirtualAddressMap() to UEFI stub
Quoted 15 lines · Ard Biesheuvel
Quoted 15 lines
Quoted 6 lines
Quoted 4 lines
Quoted 1 line
+
kernel_neon_begin(); /* disables preemption */ \Same nitpick.
Is there anything wrong with that?
I said nitpick.
My (very minor) objection is that a (very reasonable) comment is added to existing functionality by a patch that adds new functionality. It makes the git blame/praise output less clear.
Quoted 1 line
Would you prefer the comment to be on a separate line?
Quoted 8 lines
Quoted 3 lines
I would _prefer_ the comments to be a separate patch. But again, a nitpick.
Well, adding the comment is relevant to this patch, as we need to disable preemption now before switching to the new address space. In fact, it might be better even to drop the comment, and add an explicit (if redundant) preempt_disable/preempt_enable pair.
That would be more clear, yes.
/
Leif
PATCH v4 7/8 arm64/efi: remove free_boot_services() and friends
In reply to Ard BiesheuvelNow that we are calling SetVirtualAddressMap() from the stub, there is no need to reserve boot-only memory regions, which implies that there is also no reason to free them again later.
--- arch/arm64/kernel/efi.c | 123 +----------------------------------------------- 1 file changed, 1 insertion(+), 122 deletions(-)
arch/arm64/kernel/efi.c +1 -122
@@ -198,9 +198,7 @@ static __init void reserve_regions(void)if (is_normal_ram (md))early_init_dt_add_memory_arch (paddr, size); -if (is_reserve_region (md) || - md->type ==EFI_BOOT_SERVICES_CODE || - md->type ==EFI_BOOT_SERVICES_DATA ) { +if (is_reserve_region (md)) {memblock_reserve (paddr, size);if (uefi_debug)pr_cont ("*" );
@@ -213,123 +211,6 @@ static __init void reserve_regions(void)set_bit (EFI_MEMMAP , &efi.flags); } - -static u64 __init free_one_region (u64 start,u64 end) -{ -u64 size = end - start; - -if (uefi_debug) -pr_info (" EFI freeing: 0x%012llx-0x%012llx\n" , start, end -1 ); - -free_bootmem_late (start, size); -return size; -} - -static u64 __init free_region (u64 start,u64 end) -{ -u64 map_start, map_end, total =0 ; - -if (end <= start) -return total; - - map_start = (u64 )memmap.phys_map; - map_end =PAGE_ALIGN (map_start + (memmap.map_end - memmap.map)); - map_start &=PAGE_MASK ; - -if (start < map_end && end > map_start) { -/* region overlaps UEFI memmap */ -if (start < map_start) - total +=free_one_region (start, map_start); - -if (map_end < end) - total +=free_one_region (map_end, end); - }else - total +=free_one_region (start, end); - -return total; -} - -static void __init free_boot_services (void ) -{ -u64 total_freed =0 ; -u64 keep_end, free_start, free_end; -efi_memory_desc_t *md; - -/* -* If kernel uses larger pages than UEFI, we have to be careful -* not to inadvertantly free memory we want to keep if there is -* overlap@the kernel page size alignment. We do not want to -* free is_reserve_region() memory nor the UEFI memmap itself. -* -* The memory map is sorted, so we keep track of the end of -* any previous region we want to keep, remember any region -* we want to free and defer freeing it until we encounter -* the next region we want to keep. This way, before freeing -* it, we can clip it as needed to avoid freeing memory we -* want to keep for UEFI. -*/ - - keep_end =0 ; - free_start =0 ; - -for_each_efi_memory_desc (&memmap, md) { -u64 paddr, npages, size; - -if (is_reserve_region (md)) { -/* -* We don't want to free any memory from this region. -*/ -if (free_start) { -/* adjust free_end then free region */ -if (free_end > md->phys_addr) - free_end -=PAGE_SIZE ; - total_freed +=free_region (free_start, free_end); - free_start =0 ; - } - keep_end = md->phys_addr + (md->num_pages <<EFI_PAGE_SHIFT ); -continue ; - } - -if (md->type !=EFI_BOOT_SERVICES_CODE && - md->type !=EFI_BOOT_SERVICES_DATA ) { -/* no need to free this region */ -continue ; - } - -/* -* We want to free memory from this region. -*/ - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; - -if (free_start) { -if (paddr <= free_end) - free_end = paddr + size; -else { - total_freed +=free_region (free_start, free_end); - free_start = paddr; - free_end = paddr + size; - } - }else { - free_start = paddr; - free_end = paddr + size; - } -if (free_start < keep_end) { - free_start +=PAGE_SIZE ; -if (free_start >= free_end) - free_start =0 ; - } - } -if (free_start) - total_freed +=free_region (free_start, free_end); - -if (total_freed) -pr_info ("Freed 0x%llx bytes of EFI boot services memory" , - total_freed); -} -void __init efi_init (void ) {struct efi_fdt_params params;
@@ -396,8 +277,6 @@ static int __init arm64_enter_virtual_mode(void) }set_bit (EFI_SYSTEM_TABLES , &efi.flags); -free_boot_services (); -if (!efi_enabled (EFI_VIRTMAP )) {pr_err ("No UEFI virtual mapping was installed -- runtime services will not be available\n" );return -1 ;
Signature · 1 line
1.8.3.2
PATCH v4 7/8 arm64/efi: remove free_boot_services() and friends
Quoted 159 lines · Ard Biesheuvel
Now that we are calling
SetVirtualAddressMap()from the stub, there is no need to reserve boot-only memory regions, which implies that there is also no reason to free them again later.Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/kernel/efi.c | 123 +----------------------------------------------- 1 file changed, 1 insertion(+), 122 deletions(-)arch/arm64/kernel/efi.c +1
-122@@ -198,9 +198,7 @@ static __init void reserve_regions(void)if (is_normal_ram (md))early_init_dt_add_memory_arch (paddr, size); -if (is_reserve_region (md) || - md->type ==EFI_BOOT_SERVICES_CODE || - md->type ==EFI_BOOT_SERVICES_DATA ) { +if (is_reserve_region (md)) {memblock_reserve (paddr, size);if (uefi_debug)pr_cont ("*" );@@ -213,123 +211,6 @@ static __init void reserve_regions(void)set_bit (EFI_MEMMAP , &efi.flags); } - -static u64 __init free_one_region (u64 start,u64 end) -{ -u64 size = end - start; - -if (uefi_debug) -pr_info (" EFI freeing: 0x%012llx-0x%012llx\n" , start, end -1 ); - -free_bootmem_late (start, size); -return size; -} - -static u64 __init free_region (u64 start,u64 end) -{ -u64 map_start, map_end, total =0 ; - -if (end <= start) -return total; - - map_start = (u64 )memmap.phys_map; - map_end =PAGE_ALIGN (map_start + (memmap.map_end - memmap.map)); - map_start &=PAGE_MASK ; - -if (start < map_end && end > map_start) { -/* region overlaps UEFI memmap */ -if (start < map_start) - total +=free_one_region (start, map_start); - -if (map_end < end) - total +=free_one_region (map_end, end); - }else - total +=free_one_region (start, end); - -return total; -} - -static void __init free_boot_services (void ) -{ -u64 total_freed =0 ; -u64 keep_end, free_start, free_end; -efi_memory_desc_t *md; - -/* -* If kernel uses larger pages than UEFI, we have to be careful -* not to inadvertantly free memory we want to keep if there is -* overlap at the kernel page size alignment. We do not want to -* free is_reserve_region() memory nor the UEFI memmap itself. -* -* The memory map is sorted, so we keep track of the end of -* any previous region we want to keep, remember any region -* we want to free and defer freeing it until we encounter -* the next region we want to keep. This way, before freeing -* it, we can clip it as needed to avoid freeing memory we -* want to keep for UEFI. -*/ - - keep_end =0 ; - free_start =0 ; - -for_each_efi_memory_desc (&memmap, md) { -u64 paddr, npages, size; - -if (is_reserve_region (md)) { -/* -* We don't want to free any memory from this region. -*/ -if (free_start) { -/* adjust free_end then free region */ -if (free_end > md->phys_addr) - free_end -=PAGE_SIZE ; - total_freed +=free_region (free_start, free_end); - free_start =0 ; - } - keep_end = md->phys_addr + (md->num_pages <<EFI_PAGE_SHIFT ); -continue ; - } - -if (md->type !=EFI_BOOT_SERVICES_CODE && - md->type !=EFI_BOOT_SERVICES_DATA ) { -/* no need to free this region */ -continue ; - } - -/* -* We want to free memory from this region. -*/ - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; - -if (free_start) { -if (paddr <= free_end) - free_end = paddr + size; -else { - total_freed +=free_region (free_start, free_end); - free_start = paddr; - free_end = paddr + size; - } - }else { - free_start = paddr; - free_end = paddr + size; - } -if (free_start < keep_end) { - free_start +=PAGE_SIZE ; -if (free_start >= free_end) - free_start =0 ; - } - } -if (free_start) - total_freed +=free_region (free_start, free_end); - -if (total_freed) -pr_info ("Freed 0x%llx bytes of EFI boot services memory" , - total_freed); -} -void __init efi_init (void ) {struct efi_fdt_params params;@@ -396,8 +277,6 @@ static int __init arm64_enter_virtual_mode(void) }set_bit (EFI_SYSTEM_TABLES , &efi.flags); -free_boot_services (); -if (!efi_enabled (EFI_VIRTMAP )) {pr_err ("No UEFI virtual mapping was installed -- runtime services will not be available\n" );return -1 ;Signature · 1 line
1.8.3.2
PATCH v4 8/8 arm64/efi: remove idmap manipulations from UEFI code
In reply to Ard BiesheuvelNow that we have moved the call to SetVirtualAddressMap() to the stub, UEFI has no use for the ID map, so we can drop the code that installs ID mappings for UEFI memory regions.
--- arch/arm64/include/asm/efi.h | 2 -- arch/arm64/include/asm/mmu.h | 2 -- arch/arm64/kernel/efi.c | 30 ------------------------------ arch/arm64/kernel/setup.c | 1 - arch/arm64/mm/mmu.c | 12 ------------ 5 files changed, 47 deletions(-)
arch/arm64/include/asm/efi.h +0 -2
@@ -6,11 +6,9 @@#ifdef CONFIG_EFI extern void efi_init (void ); -extern void efi_idmap_init (void );extern void efi_virtmap_init (void );#else #define efi_init () -#define efi_idmap_init ()#define efi_virtmap_init#endif
arch/arm64/include/asm/mmu.h +0 -2
@@ -31,8 +31,6 @@ extern void paging_init(void);extern void setup_mm_for_reboot (void );extern void __iomem *early_io_map (phys_addr_t phys,unsigned long virt);extern void init_mem_pgprot (void ); -/* create an identity mapping for memory (or io if map_io is true) */ -extern void create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io);extern void create_pgd_mapping (struct mm_struct *mm,phys_addr_t phys,unsigned long virt,phys_addr_t size,pgprot_t prot);
arch/arm64/kernel/efi.c +0 -30
@@ -53,27 +53,6 @@ static int __init is_normal_ram(efi_memory_desc_t *md)return 0 ; } -static void __init efi_setup_idmap (void ) -{ -struct memblock_region *r; -efi_memory_desc_t *md; -u64 paddr, npages, size; - -for_each_memblock (memory, r) -create_id_mapping (r->base, r->size,0 ); - -/* map runtime io spaces */ -for_each_efi_memory_desc (&memmap, md) { -if (!(md->attribute &EFI_MEMORY_RUNTIME ) ||is_normal_ram (md)) -continue ; - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; -create_id_mapping (paddr, size,1 ); - } -} -/* * Translate a EFI virtual address into a physical address: this is necessary, * as some data members of the EFI system table are virtually remapped after
@@ -235,15 +214,6 @@ void __init efi_init(void)reserve_regions (); } -void __init efi_idmap_init (void ) -{ -if (!efi_enabled (EFI_BOOT )) -return ; - -/* boot time idmap_pg_dir is incomplete, so fill in missing parts */ -efi_setup_idmap (); -} -static int __init arm64_enter_virtual_mode (void ) {u64 mapsize;
arch/arm64/kernel/setup.c +0 -1
@@ -401,7 +401,6 @@ void __init setup_arch(char **cmdline_p)paging_init ();request_standard_resources (); -efi_idmap_init ();efi_virtmap_init ();unflatten_device_tree ();
arch/arm64/mm/mmu.c +0 -12
@@ -271,18 +271,6 @@ static void __init create_mapping(phys_addr_t phys, unsigned long virt, size, PAGE_KERNEL_EXEC); } -void __init create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io) -{ -if ((addr >>PGDIR_SHIFT ) >=ARRAY_SIZE (idmap_pg_dir)) { -pr_warn ("BUG: not creating id mapping for %pa\n" , &addr); -return ; - } -__create_mapping (&init_mm, &idmap_pg_dir[pgd_index (addr)], - addr, addr, size, - map_io ?__pgprot (PROT_DEVICE_nGnRE) - :PAGE_KERNEL_EXEC ); -} -void __init create_pgd_mapping (struct mm_struct *mm,phys_addr_t phys,unsigned long virt,phys_addr_t size,pgprot_t prot)
Signature · 1 line
1.8.3.2
PATCH v4 8/8 arm64/efi: remove idmap manipulations from UEFI code
Quoted 127 lines · Ard Biesheuvel
Now that we have moved the call to
SetVirtualAddressMap()to the stub, UEFI has no use for the ID map, so we can drop the code that installs ID mappings for UEFI memory regions.Signed-off-by Ard Biesheuvel <[email protected]>--- arch/arm64/include/asm/efi.h | 2 -- arch/arm64/include/asm/mmu.h | 2 -- arch/arm64/kernel/efi.c | 30 ------------------------------ arch/arm64/kernel/setup.c | 1 - arch/arm64/mm/mmu.c | 12 ------------ 5 files changed, 47 deletions(-)arch/arm64/include/asm/efi.h +0
-2@@ -6,11 +6,9 @@#ifdef CONFIG_EFI extern void efi_init (void ); -extern void efi_idmap_init (void );extern void efi_virtmap_init (void );#else #define efi_init () -#define efi_idmap_init ()#define efi_virtmap_init#endif arch/arm64/include/asm/mmu.h +0
-2@@ -31,8 +31,6 @@ extern void paging_init(void);extern void setup_mm_for_reboot (void );extern void __iomem *early_io_map (phys_addr_t phys,unsigned long virt);extern void init_mem_pgprot (void ); -/* create an identity mapping for memory (or io if map_io is true) */ -extern void create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io);extern void create_pgd_mapping (struct mm_struct *mm,phys_addr_t phys,unsigned long virt,phys_addr_t size,pgprot_t prot);arch/arm64/kernel/efi.c +0
-30@@ -53,27 +53,6 @@ static int __init is_normal_ram(efi_memory_desc_t *md)return 0 ; } -static void __init efi_setup_idmap (void ) -{ -struct memblock_region *r; -efi_memory_desc_t *md; -u64 paddr, npages, size; - -for_each_memblock (memory, r) -create_id_mapping (r->base, r->size,0 ); - -/* map runtime io spaces */ -for_each_efi_memory_desc (&memmap, md) { -if (!(md->attribute &EFI_MEMORY_RUNTIME ) ||is_normal_ram (md)) -continue ; - paddr = md->phys_addr; - npages = md->num_pages; -memrange_efi_to_native (&paddr, &npages); - size = npages <<PAGE_SHIFT ; -create_id_mapping (paddr, size,1 ); - } -} -/* * Translate a EFI virtual address into a physical address: this is necessary, * as some data members of the EFI system table are virtually remapped after @@ -235,15 +214,6 @@ void __init efi_init(void)reserve_regions (); } -void __init efi_idmap_init (void ) -{ -if (!efi_enabled (EFI_BOOT )) -return ; - -/* boot time idmap_pg_dir is incomplete, so fill in missing parts */ -efi_setup_idmap (); -} -static int __init arm64_enter_virtual_mode (void ) {u64 mapsize;arch/arm64/kernel/setup.c +0
-1@@ -401,7 +401,6 @@ void __init setup_arch(char **cmdline_p)paging_init ();request_standard_resources (); -efi_idmap_init ();efi_virtmap_init ();unflatten_device_tree ();arch/arm64/mm/mmu.c +0
-12@@ -271,18 +271,6 @@ static void __init create_mapping(phys_addr_t phys, unsigned long virt, size, PAGE_KERNEL_EXEC); } -void __init create_id_mapping (phys_addr_t addr,phys_addr_t size,int map_io) -{ -if ((addr >>PGDIR_SHIFT ) >=ARRAY_SIZE (idmap_pg_dir)) { -pr_warn ("BUG: not creating id mapping for %pa\n" , &addr); -return ; - } -__create_mapping (&init_mm, &idmap_pg_dir[pgd_index (addr)], - addr, addr, size, - map_io ?__pgprot (PROT_DEVICE_nGnRE) - :PAGE_KERNEL_EXEC ); -} -void __init create_pgd_mapping (struct mm_struct *mm,phys_addr_t phys,unsigned long virt,phys_addr_t size,pgprot_t prot)Signature · 1 line
1.8.3.2
So, this one will clearly need to be reworked if it is to fit on top of the patches I sent out today. However, this is trivial rework, so: