Lines Matching refs:kernel

8 is relevant to all public releases of the AArch64 Linux kernel.
17 is passed to the Linux kernel.  This may include secure monitor and
26 3. Decompress the kernel image
27 4. Call the kernel image
36 kernel will use for volatile data storage in the system.  It performs
49 the first 512 megabytes from the start of the kernel image and must not
50 cross a 2-megabyte boundary. This is to allow the kernel to map the
54 3. Decompress the kernel image
59 The AArch64 kernel does not currently provide a decompressor and
66 4. Call the kernel image
71 The decompressed kernel image contains a 64-byte header as follows:
77   u64 flags;			/* kernel flags, little endian */
98   endianness of the kernel.  Where image_size is non-zero image_size is
108   memory as possible free for use by the kernel immediately after the
109   end of the kernel image. The amount of space required will vary
117 use by the kernel.
119 Any memory described to the kernel (even that below the 2MB aligned base
120 address) which is not marked as reserved from the kernel e.g. with a
122 the kernel.
124 Before jumping into the kernel, the following conditions must be met:
145   The address range corresponding to the loaded kernel image must be
157   kernel at EL1, CNTHCTL_EL2 must have EL1PCTEN (bit 0) set where
161   All CPUs to be booted by the kernel must be part of the same coherency
162   domain on entry to the kernel.  This may require IMPLEMENTATION DEFINED
168   the kernel image will be entered must be initialised by software at a
175   - If the kernel is entered at EL1:
181 enter the kernel in the same exception level.
183 The boot loader is expected to enter the kernel on each CPU in the
187   kernel image.  The device tree blob passed by this CPU must contain
192   properties and insert them into the blob prior to kernel entry.
198   These CPUs should spin outside of the kernel in a reserved area of
199   memory (communicated to the kernel by a /memreserve/ region in the
210   the kernel (i.e. outside of the regions of memory described to the
211   kernel in the memory node, or in a reserved area of memory described
212   to the kernel by a /memreserve/ region in the device tree).  The
213   kernel will issue CPU_ON calls as described in ARM document number ARM
215   processors") to bring CPUs into the kernel.