Linux & Memory Maps: Presented By: Abdul Qadeer

Presented in Open Source Series Workshop 2010
Linux & Memory Maps

Presented by : Abdul Qadeer
22-24 December, 2010 ICOSST 2010
Dont confuse physical & virtual address spaces
Virtual address space

No one understands that outside the processor!
Physical address space

You need that to do memory operations and many
other I/O operations
int x = 25;
int address_of_x = &x;
The C / C++ address of operator (&). Does it
return a virtual address or a physical address?
VAS > PAS

Probably a normal scenario
VAS == PAS
E.g. 32 bit VAS and 4GiB installed DRAM
Some DRAM might go un-used and hence wasted!
VAS < PAS

Not a common scenario
Might be used to physically isolate DRAM used by
programs
Physical address extension; 32 bit VAS, 36bit PAS
4
Can look VAS and PAS in /proc/cpuinfo
Memory mapped I/O

Part of PAS assigned to a device
Writing to this mem => writing to device
Reading from this mem => reading from device
Devices negotiate for their required MMI/O region
Old, dumb devices (e.g. ISA devices)
Newer, smarter devices (e.g. PCIe devices)
DMA concerns
MMI/O usage needs special care

No compiler optimization (e.g. by using O0)
No pipeline reordering (use Linux read / write barriers)
Disable caching (e.g. using bits in TLB)
6
Memory mapped I/O
MMI/O PAS not usable as normal DRAM

MMI/O does not take away actual DRAM!
But does take away a region of PAS
The corresponding DRAM might go wasted
Relocate actual DRAM to elsewhere

VAS should be big enough for relocation
Chipset should allow relocation
Memory mapped I/O
Can look PAS allocation in /proc/iomem
Processor,
North & South Bridges
Picture taken from Gustavo Duarte blog accessible at: http://duartes.org/gustavo/blog/post/motherboard-chipsets-memory-map
Processor,
Processor
10
Processor,
Processor
Memory & Graphics

Controller Hub
11
Processor,
Processor
Memory
Memory & Graphics

Controller Hub
12
Processor,
Processor
Memory
Memory & Graphics

Controller Hub
I/O Controller Hub
13
MTRR registers
Memory region registration process

MTTR registers used
BIOS tells some regions initially
OS tries to find out the optimal registration
Looking Linux log in dmesg

Shows interesting system information
14
MTRR registers
15
MTRR registers
16
MTRR registers
17
How an Intel processor starts from 0XFF FF FF F0
Reset vector
All grey stuff is

memory mapped
Picture taken from Gustavo Duarte blog accessible at: http://duartes.org/gustavo/blog/post/how-computers-boot-up/
18
How an Intel processor starts from 0XFF FF FF F0

Jump to main BIOS
Reset vector
All grey stuff is

memory mapped
This is due to X86

legacy
Picture taken from Gustavo Duarte blog accessible at: http://duartes.org/gustavo/blog/post/how-computers-boot-up/
19
VAS distribution among Kernel and a user space process
3G/1G split
Theoretically 2^32 VAS available to a process
Kernel is mapped for every process for
performance reasons
Can change this split at kernel compile time to say
2G/2G or by a patch to 4G/4G
Half / Half split in 64 bit systems

128 TB for processes and Kernel
20
VAS distribution among Kernel and a user space process
32bit System
64bit System
Picture taken from http://blogs.technet.com/b/markrussinovich/archive/2008/11/17/3155406.aspx?PageIndex=6 and http://en.wikipedia.org/wiki/X86-64
21
Process address space
Process can use almost any part of user-VAS
Figure taken from Virtual Machines, versatile platforms for systems and processes, ISBN-10: 1558609105
22

Application binary interface (ABI)
Conventions
23

Conventions
Binary file format

ELF, COFF
Language run-time
C, C++ etc.
OS conventions
Loader, linker
24

Conventions
Binary file format

ELF, COFF
Language run-time
C, C++ etc.
OS conventions
Loader, linker
25
Guard pages
Not everything in VAS is mapped

Address 0 is invalid
Guard page between stack and
heap
Similar guard pages for thread
stack
26
Guard pages
See process virtual address map
cat /proc/1/maps
Address Range
Rights Offset
Device
or cat /proc/self/maps
Inode
File Associated
27
Learn how your computer is using memory
Use Linux
May be via live CDs
Compare address spaces

32 bit
64 bit
Specially interesting if you have 4 GiB or more
installed memory
28
Linux & Memory Maps
29

Linux & Memory Maps: Presented By: Abdul Qadeer

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Linux & Memory Maps: Presented By: Abdul Qadeer

Caricato da

Copyright:

Formati disponibili

Presented in Open Source Series Workshop 2010