2012-03-05 04:49:27 -07:00
|
|
|
Booting AArch64 Linux
|
|
|
|
=====================
|
|
|
|
|
|
|
|
Author: Will Deacon <will.deacon@arm.com>
|
|
|
|
Date : 07 September 2012
|
|
|
|
|
|
|
|
This document is based on the ARM booting document by Russell King and
|
|
|
|
is relevant to all public releases of the AArch64 Linux kernel.
|
|
|
|
|
|
|
|
The AArch64 exception model is made up of a number of exception levels
|
|
|
|
(EL0 - EL3), with EL0 and EL1 having a secure and a non-secure
|
|
|
|
counterpart. EL2 is the hypervisor level and exists only in non-secure
|
|
|
|
mode. EL3 is the highest priority level and exists only in secure mode.
|
|
|
|
|
|
|
|
For the purposes of this document, we will use the term `boot loader'
|
|
|
|
simply to define all software that executes on the CPU(s) before control
|
|
|
|
is passed to the Linux kernel. This may include secure monitor and
|
|
|
|
hypervisor code, or it may just be a handful of instructions for
|
|
|
|
preparing a minimal boot environment.
|
|
|
|
|
|
|
|
Essentially, the boot loader should provide (as a minimum) the
|
|
|
|
following:
|
|
|
|
|
|
|
|
1. Setup and initialise the RAM
|
|
|
|
2. Setup the device tree
|
|
|
|
3. Decompress the kernel image
|
|
|
|
4. Call the kernel image
|
|
|
|
|
|
|
|
|
|
|
|
1. Setup and initialise RAM
|
|
|
|
---------------------------
|
|
|
|
|
|
|
|
Requirement: MANDATORY
|
|
|
|
|
|
|
|
The boot loader is expected to find and initialise all RAM that the
|
|
|
|
kernel will use for volatile data storage in the system. It performs
|
|
|
|
this in a machine dependent manner. (It may use internal algorithms
|
|
|
|
to automatically locate and size all RAM, or it may use knowledge of
|
|
|
|
the RAM in the machine, or any other method the boot loader designer
|
|
|
|
sees fit.)
|
|
|
|
|
|
|
|
|
|
|
|
2. Setup the device tree
|
|
|
|
-------------------------
|
|
|
|
|
|
|
|
Requirement: MANDATORY
|
|
|
|
|
2015-06-01 05:40:32 -06:00
|
|
|
The device tree blob (dtb) must be placed on an 8-byte boundary and must
|
|
|
|
not exceed 2 megabytes in size. Since the dtb will be mapped cacheable
|
|
|
|
using blocks of up to 2 megabytes in size, it must not be placed within
|
|
|
|
any 2M region which must be mapped with any specific attributes.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
2015-06-01 05:40:32 -06:00
|
|
|
NOTE: versions prior to v4.2 also require that the DTB be placed within
|
|
|
|
the 512 MB region starting at text_offset bytes below the kernel Image.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
3. Decompress the kernel image
|
|
|
|
------------------------------
|
|
|
|
|
|
|
|
Requirement: OPTIONAL
|
|
|
|
|
|
|
|
The AArch64 kernel does not currently provide a decompressor and
|
|
|
|
therefore requires decompression (gzip etc.) to be performed by the boot
|
|
|
|
loader if a compressed Image target (e.g. Image.gz) is used. For
|
|
|
|
bootloaders that do not implement this requirement, the uncompressed
|
|
|
|
Image target is available instead.
|
|
|
|
|
|
|
|
|
|
|
|
4. Call the kernel image
|
|
|
|
------------------------
|
|
|
|
|
|
|
|
Requirement: MANDATORY
|
|
|
|
|
2013-08-14 17:10:00 -06:00
|
|
|
The decompressed kernel image contains a 64-byte header as follows:
|
2012-03-05 04:49:27 -07:00
|
|
|
|
2013-08-14 17:10:00 -06:00
|
|
|
u32 code0; /* Executable code */
|
|
|
|
u32 code1; /* Executable code */
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
u64 text_offset; /* Image load offset, little endian */
|
|
|
|
u64 image_size; /* Effective Image size, little endian */
|
|
|
|
u64 flags; /* kernel flags, little endian */
|
2012-03-05 04:49:27 -07:00
|
|
|
u64 res2 = 0; /* reserved */
|
2013-08-14 17:10:00 -06:00
|
|
|
u64 res3 = 0; /* reserved */
|
|
|
|
u64 res4 = 0; /* reserved */
|
|
|
|
u32 magic = 0x644d5241; /* Magic number, little endian, "ARM\x64" */
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
u32 res5; /* reserved (used for PE COFF offset) */
|
2013-08-14 17:10:00 -06:00
|
|
|
|
|
|
|
|
|
|
|
Header notes:
|
|
|
|
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
- As of v3.17, all fields are little endian unless stated otherwise.
|
|
|
|
|
2013-08-14 17:10:00 -06:00
|
|
|
- code0/code1 are responsible for branching to stext.
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
|
2013-11-29 14:00:14 -07:00
|
|
|
- when booting through EFI, code0/code1 are initially skipped.
|
|
|
|
res5 is an offset to the PE header and the PE header has the EFI
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
entry point (efi_stub_entry). When the stub has done its work, it
|
2013-11-29 14:00:14 -07:00
|
|
|
jumps to code0 to resume the normal boot process.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
arm64: Update the Image header
Currently the kernel Image is stripped of everything past the initial
stack, and at runtime the memory is initialised and used by the kernel.
This makes the effective minimum memory footprint of the kernel larger
than the size of the loaded binary, though bootloaders have no mechanism
to identify how large this minimum memory footprint is. This makes it
difficult to choose safe locations to place both the kernel and other
binaries required at boot (DTB, initrd, etc), such that the kernel won't
clobber said binaries or other reserved memory during initialisation.
Additionally when big endian support was added the image load offset was
overlooked, and is currently of an arbitrary endianness, which makes it
difficult for bootloaders to make use of it. It seems that bootloaders
aren't respecting the image load offset at present anyway, and are
assuming that offset 0x80000 will always be correct.
This patch adds an effective image size to the kernel header which
describes the amount of memory from the start of the kernel Image binary
which the kernel expects to use before detecting memory and handling any
memory reservations. This can be used by bootloaders to choose suitable
locations to load the kernel and/or other binaries such that the kernel
will not clobber any memory unexpectedly. As before, memory reservations
are required to prevent the kernel from clobbering these locations
later.
Both the image load offset and the effective image size are forced to be
little-endian regardless of the native endianness of the kernel to
enable bootloaders to load a kernel of arbitrary endianness. Bootloaders
which wish to make use of the load offset can inspect the effective
image size field for a non-zero value to determine if the offset is of a
known endianness. To enable software to determine the endinanness of the
kernel as may be required for certain use-cases, a new flags field (also
little-endian) is added to the kernel header to export this information.
The documentation is updated to clarify these details. To discourage
future assumptions regarding the value of text_offset, the value at this
point in time is removed from the main flow of the documentation (though
kept as a compatibility note). Some minor formatting issues in the
documentation are also corrected.
Signed-off-by: Mark Rutland <mark.rutland@arm.com>
Acked-by: Tom Rini <trini@ti.com>
Cc: Geoff Levand <geoff@infradead.org>
Cc: Kevin Hilman <kevin.hilman@linaro.org>
Acked-by: Will Deacon <will.deacon@arm.com>
Signed-off-by: Catalin Marinas <catalin.marinas@arm.com>
2014-06-24 09:51:36 -06:00
|
|
|
- Prior to v3.17, the endianness of text_offset was not specified. In
|
|
|
|
these cases image_size is zero and text_offset is 0x80000 in the
|
|
|
|
endianness of the kernel. Where image_size is non-zero image_size is
|
|
|
|
little-endian and must be respected. Where image_size is zero,
|
|
|
|
text_offset can be assumed to be 0x80000.
|
|
|
|
|
|
|
|
- The flags field (introduced in v3.17) is a little-endian 64-bit field
|
|
|
|
composed as follows:
|
|
|
|
Bit 0: Kernel endianness. 1 if BE, 0 if LE.
|
|
|
|
Bits 1-63: Reserved.
|
|
|
|
|
|
|
|
- When image_size is zero, a bootloader should attempt to keep as much
|
|
|
|
memory as possible free for use by the kernel immediately after the
|
|
|
|
end of the kernel image. The amount of space required will vary
|
|
|
|
depending on selected features, and is effectively unbound.
|
|
|
|
|
|
|
|
The Image must be placed text_offset bytes from a 2MB aligned base
|
|
|
|
address near the start of usable system RAM and called there. Memory
|
|
|
|
below that base address is currently unusable by Linux, and therefore it
|
|
|
|
is strongly recommended that this location is the start of system RAM.
|
|
|
|
At least image_size bytes from the start of the image must be free for
|
|
|
|
use by the kernel.
|
|
|
|
|
|
|
|
Any memory described to the kernel (even that below the 2MB aligned base
|
|
|
|
address) which is not marked as reserved from the kernel e.g. with a
|
|
|
|
memreserve region in the device tree) will be considered as available to
|
|
|
|
the kernel.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
Before jumping into the kernel, the following conditions must be met:
|
|
|
|
|
|
|
|
- Quiesce all DMA capable devices so that memory does not get
|
|
|
|
corrupted by bogus network packets or disk data. This will save
|
|
|
|
you many hours of debug.
|
|
|
|
|
|
|
|
- Primary CPU general-purpose register settings
|
|
|
|
x0 = physical address of device tree blob (dtb) in system RAM.
|
|
|
|
x1 = 0 (reserved for future use)
|
|
|
|
x2 = 0 (reserved for future use)
|
|
|
|
x3 = 0 (reserved for future use)
|
|
|
|
|
|
|
|
- CPU mode
|
|
|
|
All forms of interrupts must be masked in PSTATE.DAIF (Debug, SError,
|
|
|
|
IRQ and FIQ).
|
|
|
|
The CPU must be in either EL2 (RECOMMENDED in order to have access to
|
|
|
|
the virtualisation extensions) or non-secure EL1.
|
|
|
|
|
|
|
|
- Caches, MMUs
|
|
|
|
The MMU must be off.
|
|
|
|
Instruction cache may be on or off.
|
2014-03-26 12:25:55 -06:00
|
|
|
The address range corresponding to the loaded kernel image must be
|
|
|
|
cleaned to the PoC. In the presence of a system cache or other
|
|
|
|
coherent masters with caches enabled, this will typically require
|
|
|
|
cache maintenance by VA rather than set/way operations.
|
|
|
|
System caches which respect the architected cache maintenance by VA
|
|
|
|
operations must be configured and may be enabled.
|
|
|
|
System caches which do not respect architected cache maintenance by VA
|
|
|
|
operations (not recommended) must be configured and disabled.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
- Architected timers
|
2013-10-11 07:52:07 -06:00
|
|
|
CNTFRQ must be programmed with the timer frequency and CNTVOFF must
|
|
|
|
be programmed with a consistent value on all CPUs. If entering the
|
|
|
|
kernel at EL1, CNTHCTL_EL2 must have EL1PCTEN (bit 0) set where
|
|
|
|
available.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
- Coherency
|
|
|
|
All CPUs to be booted by the kernel must be part of the same coherency
|
|
|
|
domain on entry to the kernel. This may require IMPLEMENTATION DEFINED
|
|
|
|
initialisation to enable the receiving of maintenance operations on
|
|
|
|
each CPU.
|
|
|
|
|
|
|
|
- System registers
|
|
|
|
All writable architected system registers at the exception level where
|
|
|
|
the kernel image will be entered must be initialised by software at a
|
|
|
|
higher exception level to prevent execution in an UNKNOWN state.
|
|
|
|
|
2013-11-28 11:24:58 -07:00
|
|
|
For systems with a GICv3 interrupt controller:
|
|
|
|
- If EL3 is present:
|
|
|
|
ICC_SRE_EL3.Enable (bit 3) must be initialiased to 0b1.
|
|
|
|
ICC_SRE_EL3.SRE (bit 0) must be initialised to 0b1.
|
|
|
|
- If the kernel is entered at EL1:
|
|
|
|
ICC.SRE_EL2.Enable (bit 3) must be initialised to 0b1
|
|
|
|
ICC_SRE_EL2.SRE (bit 0) must be initialised to 0b1.
|
|
|
|
|
2013-10-11 07:52:07 -06:00
|
|
|
The requirements described above for CPU mode, caches, MMUs, architected
|
|
|
|
timers, coherency and system registers apply to all CPUs. All CPUs must
|
|
|
|
enter the kernel in the same exception level.
|
|
|
|
|
2012-03-05 04:49:27 -07:00
|
|
|
The boot loader is expected to enter the kernel on each CPU in the
|
|
|
|
following manner:
|
|
|
|
|
|
|
|
- The primary CPU must jump directly to the first instruction of the
|
|
|
|
kernel image. The device tree blob passed by this CPU must contain
|
2013-10-11 07:52:07 -06:00
|
|
|
an 'enable-method' property for each cpu node. The supported
|
|
|
|
enable-methods are described below.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
It is expected that the bootloader will generate these device tree
|
|
|
|
properties and insert them into the blob prior to kernel entry.
|
|
|
|
|
2013-10-11 07:52:07 -06:00
|
|
|
- CPUs with a "spin-table" enable-method must have a 'cpu-release-addr'
|
|
|
|
property in their cpu node. This property identifies a
|
|
|
|
naturally-aligned 64-bit zero-initalised memory location.
|
|
|
|
|
|
|
|
These CPUs should spin outside of the kernel in a reserved area of
|
|
|
|
memory (communicated to the kernel by a /memreserve/ region in the
|
2012-03-05 04:49:27 -07:00
|
|
|
device tree) polling their cpu-release-addr location, which must be
|
|
|
|
contained in the reserved region. A wfe instruction may be inserted
|
|
|
|
to reduce the overhead of the busy-loop and a sev will be issued by
|
|
|
|
the primary CPU. When a read of the location pointed to by the
|
2013-10-11 07:52:07 -06:00
|
|
|
cpu-release-addr returns a non-zero value, the CPU must jump to this
|
|
|
|
value. The value will be written as a single 64-bit little-endian
|
|
|
|
value, so CPUs must convert the read value to their native endianness
|
|
|
|
before jumping to it.
|
|
|
|
|
|
|
|
- CPUs with a "psci" enable method should remain outside of
|
|
|
|
the kernel (i.e. outside of the regions of memory described to the
|
|
|
|
kernel in the memory node, or in a reserved area of memory described
|
|
|
|
to the kernel by a /memreserve/ region in the device tree). The
|
|
|
|
kernel will issue CPU_ON calls as described in ARM document number ARM
|
|
|
|
DEN 0022A ("Power State Coordination Interface System Software on ARM
|
|
|
|
processors") to bring CPUs into the kernel.
|
|
|
|
|
|
|
|
The device tree should contain a 'psci' node, as described in
|
|
|
|
Documentation/devicetree/bindings/arm/psci.txt.
|
2012-03-05 04:49:27 -07:00
|
|
|
|
|
|
|
- Secondary CPU general-purpose register settings
|
|
|
|
x0 = 0 (reserved for future use)
|
|
|
|
x1 = 0 (reserved for future use)
|
|
|
|
x2 = 0 (reserved for future use)
|
|
|
|
x3 = 0 (reserved for future use)
|