Merge tag 'arm64-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/linux-aarch64

Requirement: MANDATORY

The device tree blob (dtb) must be no bigger than 2 megabytes in size

and placed at a 2-megabyte boundary within the first 512 megabytes from

the start of the kernel image. This is to allow the kernel to map the

The device tree blob (dtb) must be placed on an 8-byte boundary within

the first 512 megabytes from the start of the kernel image and must not

cross a 2-megabyte boundary. This is to allow the kernel to map the

blob using a single section mapping in the initial page tables.

Requirement: MANDATORY

The decompressed kernel image contains a 32-byte header as follows:

The decompressed kernel image contains a 64-byte header as follows:

  u32 magic	= 0x14000008;	/* branch to stext, little-endian */

  u32 res0	= 0;		/* reserved */

  u32 code0;			/* Executable code */

  u32 code1;			/* Executable code */

  u64 text_offset;		/* Image load offset */

  u64 res0	= 0;		/* reserved */

  u64 res1	= 0;		/* reserved */

  u64 res2	= 0;		/* reserved */

  u64 res3	= 0;		/* reserved */

  u64 res4	= 0;		/* reserved */

  u32 magic	= 0x644d5241;	/* Magic number, little endian, "ARM\x64" */

  u32 res5 = 0;      		/* reserved */

Header notes:

- code0/code1 are responsible for branching to stext.

The image must be placed at the specified offset (currently 0x80000)

from the start of the system RAM and called there. The start of the

		Tagged virtual addresses in AArch64 Linux

		=========================================

Author: Will Deacon <will.deacon@arm.com>

Date  : 12 June 2013

This document briefly describes the provision of tagged virtual

addresses in the AArch64 translation system and their potential uses

in AArch64 Linux.

The kernel configures the translation tables so that translations made

via TTBR0 (i.e. userspace mappings) have the top byte (bits 63:56) of

the virtual address ignored by the translation hardware. This frees up

this byte for application use, with the following caveats:

	(1) The kernel requires that all user addresses passed to EL1

	    are tagged with tag 0x00. This means that any syscall

	    parameters containing user virtual addresses *must* have

	    their top byte cleared before trapping to the kernel.

	(2) Tags are not guaranteed to be preserved when delivering

	    signals. This means that signal handlers in applications

	    making use of tags cannot rely on the tag information for

	    user virtual addresses being maintained for fields inside

	    siginfo_t. One exception to this rule is for signals raised

	    in response to debug exceptions, where the tag information

	    will be preserved.

	(3) Special care should be taken when using tagged pointers,

	    since it is likely that C compilers will not hazard two

	    addresses differing only in the upper bits.

The architecture prevents the use of a tagged PC, so the upper byte will

be set to a sign-extension of bit 55 on exception return.

typedef struct user_fp elf_fpregset_t;

#define EM_ARM	40

#define EF_ARM_EABI_MASK	0xff000000

#define EF_ARM_EABI_UNKNOWN	0x00000000

#define EF_ARM_EABI_VER1	0x01000000

config IOMMU_HELPER

	def_bool SWIOTLB

config KERNEL_MODE_NEON

	def_bool y

source "init/Kconfig"

source "kernel/Kconfig.freezer"

typedef elf_greg_t elf_gregset_t[ELF_NGREG];

typedef struct user_fpsimd_state elf_fpregset_t;

#define EM_AARCH64		183

/*

 * AArch64 static relocation types.

 */

#define arch_randomize_brk arch_randomize_brk

#ifdef CONFIG_COMPAT

#define EM_ARM				40

#define COMPAT_ELF_PLATFORM		("v8l")

#define COMPAT_ELF_ET_DYN_BASE		(randomize_et_dyn(2 * TASK_SIZE_32 / 3))