ia64/linux-2.6.18-xen.hg

view Documentation/x86_64/mm.txt @ 524:7f8b544237bf

netfront: Allow netfront in domain 0.

This is useful if your physical network device is in a utility domain.

Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
author Keir Fraser <keir.fraser@citrix.com>
date Tue Apr 15 15:18:58 2008 +0100 (2008-04-15)
parents 831230e53067
children
line source
2 <previous description obsolete, deleted>
4 Virtual memory map with 4 level page tables:
6 0000000000000000 - 00007fffffffffff (=47bits) user space, different per mm
7 hole caused by [48:63] sign extension
8 ffff800000000000 - ffff80ffffffffff (=40bits) guard hole
9 ffff810000000000 - ffffc0ffffffffff (=46bits) direct mapping of all phys. memory
10 ffffc10000000000 - ffffc1ffffffffff (=40bits) hole
11 ffffc20000000000 - ffffe1ffffffffff (=45bits) vmalloc/ioremap space
12 ... unused hole ...
13 ffffffff80000000 - ffffffff82800000 (=40MB) kernel text mapping, from phys 0
14 ... unused hole ...
15 ffffffff88000000 - fffffffffff00000 (=1919MB) module mapping space
17 The direct mapping covers all memory in the system upto the highest
18 memory address (this means in some cases it can also include PCI memory
19 holes)
21 vmalloc space is lazily synchronized into the different PML4 pages of
22 the processes using the page fault handler, with init_level4_pgt as
23 reference.
25 Current X86-64 implementations only support 40 bit of address space,
26 but we support upto 46bits. This expands into MBZ space in the page tables.
28 -Andi Kleen, Jul 2004