Presented in Open Source Series Workshop Linux & Memory Maps. Presented by : Abdul Qadeer December, 2010 ICOSST 2010

Size: px

Start display at page:

Download "Presented in Open Source Series Workshop Linux & Memory Maps. Presented by : Abdul Qadeer December, 2010 ICOSST 2010"

Chastity Phelps
6 years ago
Views:

1 Linux & Memory Maps Presented by : Abdul Qadeer 1

2 Don t 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 2

3 Don t confuse physical & virtual address spaces intx = 25; intaddress_of_x= &x; The C / C++ address of operator (&). Does it return a virtual address or a physical address? 3

4 Don t confuse physical & virtual address spaces 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

5 Don t confuse physical & virtual address spaces Can look VAS and PAS in /proc/cpuinfo 5

6 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

7 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 7

8 Memory mapped I/O Can look PAS allocation in /proc/iomem 8

9 Processor, North & South Bridges Picture taken from Gustavo Duarte blog accessible at: 9

10 & South Bridges Processor Processor, North Picture taken from Gustavo Duarte blog accessible at: 10

11 & South Bridges Processor Memory & Graphics Controller Hub Processor, North Picture taken from Gustavo Duarte blog accessible at: 11

12 & South Bridges Memory Processor Memory & Graphics Controller Hub Processor, North Picture taken from Gustavo Duarte blog accessible at: 12

13 & South Bridges Memory Processor Memory & Graphics Controller Hub Processor, North I/O Controller Hub Picture taken from Gustavo Duarte blog accessible at: 13

14 MTRR registers Memory region registration process MTTR registers used BIOS tells some regions initially OS tries to findout the optimal registration Looking Linuxlog in dmesg Shows interesting system information 14

15 MTRR registers 15

16 MTRR registers 16

17 MTRR registers 17

18 How an Intel processor starts from 0XFF FF FFF0 Reset vector All grey stuff is memory mapped Picture taken from Gustavo Duarte blog accessible at: 18

19 How an Intel processor starts from 0XFF FF FFF0 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: 19

20 VAS distribution among Kernel and a user space process 3G/1G split Theoretically 2^32 VAS available to a process Kernelis mapped for every process for performance reasons Can change this splitat 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 andkernel 20

VAS distribution among Kernel and a user space process 32bit System 64bit System Picture taken from http://blogs.

21 VAS distribution among Kernel and a user space process 32bit System 64bit System Picture taken from and 21

22 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:

23 Process address space Process can use almost any part of user-vas Application binary interface (ABI) Conventions Figure taken from Virtual Machines, versatile platforms for systems and processes, ISBN-10:

24 Process address space Process can use almost any part of user-vas Application binary interface (ABI) Conventions Binary file format ELF, COFF Language run-time C, C++ etc. OS conventions Loader, linker Figure taken from Virtual Machines, versatile platforms for systems and processes, ISBN-10:

25 Process address space Process can use almost any part of user-vas Application binary interface (ABI) Conventions Binary file format ELF, COFF Language run-time C, C++ etc. OS conventions Loader, linker Figure taken from Virtual Machines, versatile platforms for systems and processes, ISBN-10:

26 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

27 Guard pages See process virtual address map cat /proc/1/maps or cat /proc/self/maps Address Range Rights Offset Device Inode File Associated 27

28 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 GiBor more installed memory 28

29 Linux & Memory Maps 29

COS 318: Operating Systems. Overview. Andy Bavier Computer Science Department Princeton University

COS 318: Operating Systems. Overview. Andy Bavier Computer Science Department Princeton University COS 318: Operating Systems Overview Andy Bavier Computer Science Department Princeton University http://www.cs.princeton.edu/courses/archive/fall10/cos318/ Logistics Precepts: Tue: 7:30pm-8:30pm, 105 CS