Blame view

kernel/linux-rt-4.4.41/arch/arm64/include/asm/efi.h 1.94 KB
5113f6f70   김현기   kernel add
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
  #ifndef _ASM_EFI_H
  #define _ASM_EFI_H
  
  #include <asm/io.h>
  #include <asm/neon.h>
  
  #ifdef CONFIG_EFI
  extern void efi_init(void);
  #else
  #define efi_init()
  #endif
  
  #define efi_call_virt(f, ...)						\
  ({									\
  	efi_##f##_t *__f;						\
  	efi_status_t __s;						\
  									\
  	kernel_neon_begin();						\
  	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;						\
  									\
  	kernel_neon_begin();						\
  	efi_virtmap_load();						\
  	__f = efi.systab->runtime->f;					\
  	__f(__VA_ARGS__);						\
  	efi_virtmap_unload();						\
  	kernel_neon_end();						\
  })
  
  /* arch specific definitions used by the stub code */
  
  /*
   * AArch64 requires the DTB to be 8-byte aligned in the first 512MiB from
   * start of kernel and may not cross a 2MiB boundary. We set alignment to
   * 2MiB so we know it won't cross a 2MiB boundary.
   */
  #define EFI_FDT_ALIGN	SZ_2M   /* used by allocate_new_fdt_and_exit_boot() */
  #define MAX_FDT_OFFSET	SZ_512M
  
  #define efi_call_early(f, ...) sys_table_arg->boottime->f(__VA_ARGS__)
  
  #define EFI_ALLOC_ALIGN		SZ_64K
  
  /*
   * On ARM systems, virtually remapped UEFI runtime services are set up in two
   * distinct stages:
   * - The stub retrieves the final version of the memory map from UEFI, populates
   *   the virt_addr fields and calls the SetVirtualAddressMap() [SVAM] runtime
   *   service to communicate the new mapping to the firmware (Note that the new
   *   mapping is not live at this time)
   * - During an early initcall(), the EFI system table is permanently remapped
   *   and the virtual remapping of the UEFI Runtime Services regions is loaded
   *   into a private set of page tables. If this all succeeds, the Runtime
   *   Services are enabled and the EFI_RUNTIME_SERVICES bit set.
   */
  
  void efi_virtmap_load(void);
  void efi_virtmap_unload(void);
  
  #endif /* _ASM_EFI_H */