[net-next-2.6.git] / Documentation / arm / memory.txt

		Kernel Memory Layout on ARM Linux

		Russell King <rmk@arm.linux.org.uk>
		     November 17, 2005 (2.6.15)

This document describes the virtual memory layout which the Linux
kernel uses for ARM processors.  It indicates which regions are
free for platforms to use, and which are used by generic code.

The ARM CPU is capable of addressing a maximum of 4GB virtual memory
space, and this must be shared between user space processes, the
kernel, and hardware devices.

As the ARM architecture matures, it becomes necessary to reserve
certain regions of VM space for use for new facilities; therefore
this document may reserve more VM space over time.

Start		End		Use
--------------------------------------------------------------------------
ffff8000	ffffffff	copy_user_page / clear_user_page use.
				For SA11xx and Xscale, this is used to
				setup a minicache mapping.

ffff4000	ffffffff	cache aliasing on ARMv6 and later CPUs.

ffff1000	ffff7fff	Reserved.
				Platforms must not use this address range.

ffff0000	ffff0fff	CPU vector page.
				The CPU vectors are mapped here if the
				CPU supports vector relocation (control
				register V bit.)

fffe0000	fffeffff	XScale cache flush area.  This is used
				in proc-xscale.S to flush the whole data
				cache.  Free for other usage on non-XScale.

fff00000	fffdffff	Fixmap mapping region.  Addresses provided
				by fix_to_virt() will be located here.

ffc00000	ffefffff	DMA memory mapping region.  Memory returned
				by the dma_alloc_xxx functions will be
				dynamically mapped here.

ff000000	ffbfffff	Reserved for future expansion of DMA
				mapping region.

VMALLOC_END	feffffff	Free for platform use, recommended.
				VMALLOC_END must be aligned to a 2MB
				boundary.

VMALLOC_START	VMALLOC_END-1	vmalloc() / ioremap() space.
				Memory returned by vmalloc/ioremap will
				be dynamically placed in this region.
				VMALLOC_START may be based upon the value
				of the high_memory variable.

PAGE_OFFSET	high_memory-1	Kernel direct-mapped RAM region.
				This maps the platforms RAM, and typically
				maps all platform RAM in a 1:1 relationship.

PKMAP_BASE	PAGE_OFFSET-1	Permanent kernel mappings
				One way of mapping HIGHMEM pages into kernel
				space.

MODULES_VADDR	MODULES_END-1	Kernel module space
				Kernel modules inserted via insmod are
				placed here using dynamic mappings.

00001000	TASK_SIZE-1	User space mappings
				Per-thread mappings are placed here via
				the mmap() system call.

00000000	00000fff	CPU vector page / null pointer trap
				CPUs which do not support vector remapping
				place their vector page here.  NULL pointer
				dereferences by both the kernel and user
				space are also caught via this mapping.

Please note that mappings which collide with the above areas may result
in a non-bootable kernel, or may cause the kernel to (eventually) panic
at run time.

Since future CPUs may impact the kernel mapping layout, user programs
must not access any memory which is not mapped inside their 0x0001000
to TASK_SIZE address range.  If they wish to access these areas, they
must set up their own mappings using open() and mmap().
Commit	Line	Data
1da177e4 LT	1	Kernel Memory Layout on ARM Linux
	2
	3	Russell King <rmk@arm.linux.org.uk>
02b30839	4	November 17, 2005 (2.6.15)
1da177e4 LT	5
	6	This document describes the virtual memory layout which the Linux
	7	kernel uses for ARM processors. It indicates which regions are
	8	free for platforms to use, and which are used by generic code.
	9
	10	The ARM CPU is capable of addressing a maximum of 4GB virtual memory
	11	space, and this must be shared between user space processes, the
	12	kernel, and hardware devices.
	13
	14	As the ARM architecture matures, it becomes necessary to reserve
	15	certain regions of VM space for use for new facilities; therefore
	16	this document may reserve more VM space over time.
	17
	18	Start End Use
	19	--------------------------------------------------------------------------
	20	ffff8000 ffffffff copy_user_page / clear_user_page use.
	21	For SA11xx and Xscale, this is used to
	22	setup a minicache mapping.
	23
e624859e LW	24	ffff4000 ffffffff cache aliasing on ARMv6 and later CPUs.
e624859e LW	25
1da177e4 LT	26	ffff1000 ffff7fff Reserved.
	27	Platforms must not use this address range.
	28
	29	ffff0000 ffff0fff CPU vector page.
	30	The CPU vectors are mapped here if the
	31	CPU supports vector relocation (control
	32	register V bit.)
	33
5f0fbf9e NP	34	fffe0000 fffeffff XScale cache flush area. This is used
	35	in proc-xscale.S to flush the whole data
	36	cache. Free for other usage on non-XScale.
	37
	38	fff00000 fffdffff Fixmap mapping region. Addresses provided
	39	by fix_to_virt() will be located here.
	40
	41	ffc00000 ffefffff DMA memory mapping region. Memory returned
1da177e4 LT	42	by the dma_alloc_xxx functions will be
	43	dynamically mapped here.
	44
	45	ff000000 ffbfffff Reserved for future expansion of DMA
	46	mapping region.
	47
	48	VMALLOC_END feffffff Free for platform use, recommended.
02b30839 RK	49	VMALLOC_END must be aligned to a 2MB
02b30839 RK	50	boundary.
1da177e4 LT	51
	52	VMALLOC_START VMALLOC_END-1 vmalloc() / ioremap() space.
	53	Memory returned by vmalloc/ioremap will
	54	be dynamically placed in this region.
	55	VMALLOC_START may be based upon the value
	56	of the high_memory variable.
	57
	58	PAGE_OFFSET high_memory-1 Kernel direct-mapped RAM region.
	59	This maps the platforms RAM, and typically
	60	maps all platform RAM in a 1:1 relationship.
	61
18fe1cad FB	62	PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
	63	One way of mapping HIGHMEM pages into kernel
	64	space.
	65
	66	MODULES_VADDR MODULES_END-1 Kernel module space
1da177e4 LT	67	Kernel modules inserted via insmod are
	68	placed here using dynamic mappings.
	69
	70	00001000 TASK_SIZE-1 User space mappings
	71	Per-thread mappings are placed here via
	72	the mmap() system call.
	73
	74	00000000 00000fff CPU vector page / null pointer trap
	75	CPUs which do not support vector remapping
	76	place their vector page here. NULL pointer
	77	dereferences by both the kernel and user
	78	space are also caught via this mapping.
	79
	80	Please note that mappings which collide with the above areas may result
	81	in a non-bootable kernel, or may cause the kernel to (eventually) panic
	82	at run time.
	83
	84	Since future CPUs may impact the kernel mapping layout, user programs
	85	must not access any memory which is not mapped inside their 0x0001000
	86	to TASK_SIZE address range. If they wish to access these areas, they
	87	must set up their own mappings using open() and mmap().