This section explains the steps taken during compilation of the Linux kernel and the output produced at each stage. The build process depends on the architecture so I would like to emphasize that we only consider building a Linux/x86 kernel.
When the user types 'make zImage' or 'make bzImage' the resulting bootable
kernel image is stored as
arch/i386/boot/zImage or
arch/i386/boot/bzImage respectively.
Here is how the image is built:
vmlinux which is a
statically linked, non-stripped ELF 32-bit LSB 80386 executable file.
System.map is produced by nm vmlinux, irrelevant or uninteresting
symbols are grepped out.
arch/i386/boot.
bootsect.S is preprocessed either with or without
-D__BIG_KERNEL__, depending on whether the target is
bzImage or zImage, into bbootsect.s or bootsect.s respectively.
bbootsect.s is assembled and then converted into 'raw binary' form
called bbootsect (or bootsect.s assembled and raw-converted into
bootsect for zImage).
setup.S (setup.S includes video.S) is preprocessed into
bsetup.s for bzImage or setup.s for zImage. In the same way as the
bootsector code, the difference is marked by -D__BIG_KERNEL__ present
for bzImage. The result is then converted into 'raw binary' form
called bsetup.
arch/i386/boot/compressed and convert
/usr/src/linux/vmlinux to $tmppiggy (tmp filename) in raw binary
format, removing .note and .comment ELF sections.
piggy.o.
head.S and misc.c (still in
arch/i386/boot/compressed directory) into ELF objects head.o and
misc.o.
head.o, misc.o and piggy.o into bvmlinux (or vmlinux for
zImage, don't mistake this for /usr/src/linux/vmlinux!). Note the
difference between -Ttext 0x1000 used for vmlinux and -Ttext 0x100000
for bvmlinux, i.e. for bzImage compression loader is high-loaded.
bvmlinux to 'raw binary' bvmlinux.out removing .note and
.comment ELF sections.
arch/i386/boot directory and, using the program tools/build,
cat together bbootsect, bsetup and compressed/bvmlinux.out into bzImage
(delete extra 'b' above for zImage). This writes important variables
like setup_sects and root_dev at the end of the bootsector.0x4000 bytes >= 512 + setup_sects * 512 + room for stack while running bootsector/setup
We will see later where this limitation comes from.
The upper limit on the bzImage size produced at this step is about 2.5M for booting with LILO and 0xFFFF paragraphs (0xFFFF0 = 1048560 bytes) for booting raw image, e.g. from floppy disk or CD-ROM (El-Torito emulation mode).
Note that while tools/build does validate the size of boot sector, kernel image
and lower bound of setup size, it does not check the *upper* bound of said
setup size. Therefore it is easy to build a broken kernel by just adding some
large ".space" at the end of setup.S.
The boot process details are architecture-specific, so we shall focus our attention on the IBM PC/IA32 architecture. Due to old design and backward compatibility, the PC firmware boots the operating system in an old-fashioned manner. This process can be separated into the following six logical stages:
The bootsector used to boot Linux kernel could be either:
arch/i386/boot/bootsect.S),We consider here the Linux bootsector in detail. The first few lines initialise the convenience macros to be used for segment values:
29 SETUPSECS = 4 /* default nr of setup-sectors */
30 BOOTSEG = 0x07C0 /* original address of boot-sector */
31 INITSEG = DEF_INITSEG /* we move boot here - out of the way */
32 SETUPSEG = DEF_SETUPSEG /* setup starts here */
33 SYSSEG = DEF_SYSSEG /* system loaded at 0x10000 (65536) */
34 SYSSIZE = DEF_SYSSIZE /* system size: # of 16-byte clicks */
(the numbers on the left are the line numbers of bootsect.S file)
The values of DEF_INITSEG, DEF_SETUPSEG, DEF_SYSSEG and DEF_SYSSIZE are taken
from include/asm/boot.h:
/* Don't touch these, unless you really know what you're doing. */
#define DEF_INITSEG 0x9000
#define DEF_SYSSEG 0x1000
#define DEF_SETUPSEG 0x9020
#define DEF_SYSSIZE 0x7F00
Now, let us consider the actual code of bootsect.S:
54 movw $BOOTSEG, %ax
55 movw %ax, %ds
56 movw $INITSEG, %ax
57 movw %ax, %es
58 movw $256, %cx
59 subw %si, %si
60 subw %di, %di
61 cld
62 rep
63 movsw
64 ljmp $INITSEG, $go
65 # bde - changed 0xff00 to 0x4000 to use debugger at 0x6400 up (bde). We
66 # wouldn't have to worry about this if we checked the top of memory. Also
67 # my BIOS can be configured to put the wini drive tables in high memory
68 # instead of in the vector table. The old stack might have clobbered the
69 # drive table.
70 go: movw $0x4000-12, %di # 0x4000 is an arbitrary value >=
71 # length of bootsect + length of
72 # setup + room for stack;
73 # 12 is disk parm size.
74 movw %ax, %ds # ax and es already contain INITSEG
75 movw %ax, %ss
76 movw %di, %sp # put stack at INITSEG:0x4000-12.
Lines 54-63 move the bootsector code from address 0x7C00 to 0x90000. This is achieved by:
The reason this code does not use rep movsd is intentional (hint - .code16).
Line 64 jumps to label go: in the newly made copy of the
bootsector, i.e. in segment 0x9000. This and the following three
instructions (lines 64-76) prepare the stack at $INITSEG:0x4000-12, i.e.
%ss = $INITSEG (0x9000) and %sp = 0x3FEE (0x4000-12). This is where the
limit on setup size comes from that we mentioned earlier (see Building the
Linux Kernel Image).
Lines 77-103 patch the disk parameter table for the first disk to allow multi-sector reads:
77 # Many BIOS's default disk parameter tables will not recognise
78 # multi-sector reads beyond the maximum sector number specified
79 # in the default diskette parameter tables - this may mean 7
80 # sectors in some cases.
81 #
82 # Since single sector reads are slow and out of the question,
83 # we must take care of this by creating new parameter tables
84 # (for the first disk) in RAM. We will set the maximum sector
85 # count to 36 - the most we will encounter on an ED 2.88.
86 #
87 # High doesn't hurt. Low does.
88 #
89 # Segments are as follows: ds = es = ss = cs - INITSEG, fs = 0,
90 # and gs is unused.
91 movw %cx, %fs # set fs to 0
92 movw $0x78, %bx # fs:bx is parameter table address
93 pushw %ds
94 ldsw %fs:(%bx), %si # ds:si is source
95 movb $6, %cl # copy 12 bytes
96 pushw %di # di = 0x4000-12.
97 rep # don't need cld -> done on line 66
98 movsw
99 popw %di
100 popw %ds
101 movb $36, 0x4(%di) # patch sector count
102 movw %di, %fs:(%bx)
103 movw %es, %fs:2(%bx)
The floppy disk controller is reset using BIOS service int 0x13 function 0 (reset FDC) and setup sectors are loaded immediately after the bootsector, i.e. at physical address 0x90200 ($INITSEG:0x200), again using BIOS service int 0x13, function 2 (read sector(s)). This happens during lines 107-124:
107 load_setup:
108 xorb %ah, %ah # reset FDC
109 xorb %dl, %dl
110 int $0x13
111 xorw %dx, %dx # drive 0, head 0
112 movb $0x02, %cl # sector 2, track 0
113 movw $0x0200, %bx # address = 512, in INITSEG
114 movb $0x02, %ah # service 2, "read sector(s)"
115 movb setup_sects, %al # (assume all on head 0, track 0)
116 int $0x13 # read it
117 jnc ok_load_setup # ok - continue
118 pushw %ax # dump error code
119 call print_nl
120 movw %sp, %bp
121 call print_hex
122 popw %ax
123 jmp load_setup
124 ok_load_setup:
If loading setup_sects sectors of setup code succeeded we jump to label
ok_load_setup:.
Then we proceed to load the compressed kernel image at physical
address 0x10000. This
is done to preserve the firmware data areas in low memory (0-64K).
After the kernel is loaded, we jump to $SETUPSEG:0 (arch/i386/boot/setup.S).
Once the data is no longer needed (e.g. no more calls to BIOS) it is
overwritten by moving the entire (compressed) kernel image from 0x10000 to
0x1000 (physical addresses, of course).
This is done by setup.S which sets things up for protected mode and jumps
to 0x1000 which is the head of the compressed kernel, i.e.
arch/386/boot/compressed/{head.S,misc.c}.
This sets up stack and calls decompress_kernel() which uncompresses the
kernel to address 0x100000 and jumps to it.
Note that old bootloaders (old versions of LILO) could only load the first 4 sectors of setup, which is why there is code in setup to load the rest of itself if needed. Also, the code in setup has to take care of various combinations of loader type/version vs zImage/bzImage and is therefore highly complex.
Let us examine the kludge in the bootsector code that allows to load a big
kernel, known also as "bzImage".
The setup sectors are loaded as usual at 0x90200, but the kernel is loaded
64K chunk at a time using a special helper routine that calls BIOS to move
data from low to high memory. This helper routine is referred to by
bootsect_kludge in bootsect.S and is defined as bootsect_helper in setup.S.
The bootsect_kludge label in setup.S contains the value of setup segment
and the offset of bootsect_helper code in it so that bootsector can use the lcall
instruction to jump to it (inter-segment jump).
The reason why it is in setup.S is simply because there is no more space left
in bootsect.S (which is strictly not true - there are approximatively 4 spare bytes
and at least 1 spare byte in bootsect.S but that is not enough, obviously).
This routine uses BIOS service int 0x15 (ax=0x8700) to move to high memory
and resets %es to always point to 0x10000. This ensures that the code in bootsect.S
doesn't run out of low memory when copying data from disk.
There are several advantages in using a specialised bootloader (LILO) over a bare bones Linux bootsector:
The last thing LILO does is to jump to setup.S and things proceed as normal.
By "high-level initialisation" we consider anything which is not directly
related to bootstrap, even though parts of the code to perform this are
written in asm, namely arch/i386/kernel/head.S which is the head of the
uncompressed kernel. The following steps are performed:
start_kernel(), all others call
arch/i386/kernel/smpboot.c:initialize_secondary() if ready=1,
which just reloads esp/eip and doesn't return.The init/main.c:start_kernel() is written in C and does the following:
kmem_cache_init(), initialise most of slab allocator.mem_init() which calculates max_mapnr, totalram_pages and
high_memory and prints out the "Memory: ..." line.kmem_cache_sizes_init(), finish slab allocator initialisation.fork_init(), create uid_cache, initialise max_threads based on
the amount of memory available and configure RLIMIT_NPROC for
init_task to be max_threads/2.init() which execs
execute_command if supplied via "init=" boot parameter, or tries to
exec /sbin/init, /etc/init, /bin/init, /bin/sh in this order; if
all these fail, panic with "suggestion" to use "init=" parameter.Important thing to note here that the init() kernel thread calls
do_basic_setup() which in turn calls do_initcalls() which goes through the
list of functions registered by means of __initcall or module_init() macros
and invokes them. These functions either do not depend on each other
or their dependencies have been manually fixed by the link order in the
Makefiles. This means that, depending on
the position of directories in the trees and the structure of the Makefiles,
the order in which initialisation functions are invoked can change. Sometimes, this
is important because you can imagine two subsystems A and B with B depending
on some initialisation done by A. If A is compiled statically and B is a
module then B's entry point is guaranteed to be invoked after A prepared
all the necessary environment. If A is a module, then B is also necessarily
a module so there are no problems. But what if both A and B are statically
linked into the kernel? The order in which they are invoked depends on the relative
entry point offsets in the .initcall.init ELF section of the kernel image.
Rogier Wolff proposed to introduce a hierarchical "priority" infrastructure
whereby modules could let the linker know in what (relative) order they
should be linked, but so far there are no patches available that implement
this in a sufficiently elegant manner to be acceptable into the kernel.
Therefore, make sure your link order is correct. If, in the example above,
A and B work fine when compiled statically once, they will always work,
provided they are listed sequentially in the same Makefile. If they don't
work, change the order in which their object files are listed.
Another thing worth noting is Linux's ability to execute an "alternative
init program" by means of passing "init=" boot commandline. This is useful
for recovering from accidentally overwritten /sbin/init or debugging the
initialisation (rc) scripts and /etc/inittab by hand, executing them
one at a time.
On SMP, the BP goes through the normal sequence of bootsector, setup etc
until it reaches the start_kernel(), and then on to smp_init() and
especially src/i386/kernel/smpboot.c:smp_boot_cpus(). The smp_boot_cpus()
goes in a loop for each apicid (until NR_CPUS) and calls do_boot_cpu() on
it. What do_boot_cpu() does is create (i.e. fork_by_hand) an idle task for
the target cpu and write in well-known locations defined by the Intel MP
spec (0x467/0x469) the EIP of trampoline code found in trampoline.S. Then
it generates STARTUP IPI to the target cpu which makes this AP execute the
code in trampoline.S.
The boot CPU creates a copy of trampoline code for each CPU in low memory. The AP code writes a magic number in its own code which is verified by the BP to make sure that AP is executing the trampoline code. The requirement that trampoline code must be in low memory is enforced by the Intel MP specification.
The trampoline code simply sets %bx register to 1, enters protected mode
and jumps to startup_32 which is the main entry to arch/i386/kernel/head.S.
Now, the AP starts executing head.S and discovering that it is not a BP,
it skips the code that clears BSS and then enters initialize_secondary()
which just enters the idle task for this CPU - recall that init_tasks[cpu]
was already initialised by BP executing do_boot_cpu(cpu).
Note that init_task can be shared but each idle thread must have its own
TSS. This is why init_tss[NR_CPUS] is an array.
When the operating system initialises itself, most of the code and data structures are never needed again. Most operating systems (BSD, FreeBSD etc.) cannot dispose of this unneeded information, thus wasting precious physical kernel memory. The excuse they use (see McKusick's 4.4BSD book) is that "the relevant code is spread around various subsystems and so it is not feasible to free it". Linux, of course, cannot use such excuses because under Linux "if something is possible in principle, then it is already implemented or somebody is working on it".
So, as I said earlier, Linux kernel can only be compiled as an ELF binary, and now we find out the reason (or one of the reasons) for that. The reason related to throwing away initialisation code/data is that Linux provides two macros to be used:
__init - for initialisation code__initdata - for dataThese evaluate to gcc attribute specificators (also known as "gcc magic")
as defined in include/linux/init.h:
#ifndef MODULE
#define __init __attribute__ ((__section__ (".text.init")))
#define __initdata __attribute__ ((__section__ (".data.init")))
#else
#define __init
#define __initdata
#endif
What this means is that if the code is compiled statically into the kernel
(i.e. MODULE is not defined) then it is placed in the special ELF section
.text.init, which is declared in the linker map in arch/i386/vmlinux.lds.
Otherwise (i.e. if it is a module) the macros evaluate to nothing.
What happens during boot is that the "init" kernel thread (function
init/main.c:init()) calls the arch-specific function free_initmem() which
frees all the pages between addresses __init_begin and __init_end.
On a typical system (my workstation), this results in freeing about 260K of memory.
The functions registered via module_init() are placed in .initcall.init
which is also freed in the static case. The current trend in Linux, when
designing a subsystem (not necessarily a module), is to provide
init/exit entry points from the early stages of design so that in the
future, the subsystem in question can be modularised if needed. Example of
this is pipefs, see fs/pipe.c. Even if a given subsystem will never become a
module, e.g. bdflush (see fs/buffer.c), it is still nice and tidy to use
the module_init() macro against its initialisation function, provided it does
not matter when exactly is the function called.
There are two more macros which work in a similar manner, called __exit and
__exitdata, but they are more directly connected to the module support and
therefore will be explained in a later section.
Let us recall what happens to the commandline passed to kernel during boot:
arch/i386/kernel/head.S copies the first 2k of it out to the zeropage.
Note that the current version (21) of LILO chops the commandline to
79 bytes. This is a nontrivial bug in LILO (when large EBDA support
is enabled) and Werner promised to fix it sometime soon. If you really
need to pass commandlines longer than 79 bytes then you can either
use BCP or hardcode your commandline in
arch/i386/kernel/setup.c:parse_mem_cmdline() function.
arch/i386/kernel/setup.c:parse_mem_cmdline() (called by
setup_arch(), itself called by start_kernel()) copies 256 bytes from zeropage
into saved_command_line which is displayed by /proc/cmdline. This
same routine processes the "mem=" option if present and makes appropriate
adjustments to VM parameters.
parse_options() (called by start_kernel())
which processes some "in-kernel" parameters (currently "init=" and
environment/arguments for init) and passes each word to checksetup().
checksetup() goes through the code in ELF section .setup.init and
invokes each function, passing it the word if it matches. Note that
using the return value of 0 from the function registered via __setup(),
it is possible to pass the same "variable=value" to more than one
function with "value" invalid to one and valid to another.
Jeff Garzik commented: "hackers who do that get spanked :)"
Why? Because this is clearly ld-order specific, i.e. kernel linked
in one order will have functionA invoked before functionB and another
will have it in reversed order, with the result depending on the order.
So, how do we write code that processes boot commandline? We use the __setup()
macro defined in include/linux/init.h:
/*
* Used for kernel command line parameter setup
*/
struct kernel_param {
const char *str;
int (*setup_func)(char *);
};
extern struct kernel_param __setup_start, __setup_end;
#ifndef MODULE
#define __setup(str, fn) \
static char __setup_str_##fn[] __initdata = str; \
static struct kernel_param __setup_##fn __initsetup = \
{ __setup_str_##fn, fn }
#else
#define __setup(str,func) /* nothing */
endif
So, you would typically use it in your code like this
(taken from code of real driver, BusLogic HBA drivers/scsi/BusLogic.c):
static int __init
BusLogic_Setup(char *str)
{
int ints[3];
(void)get_options(str, ARRAY_SIZE(ints), ints);
if (ints[0] != 0) {
BusLogic_Error("BusLogic: Obsolete Command Line Entry "
"Format Ignored\n", NULL);
return 0;
}
if (str == NULL || *str == '\0')
return 0;
return BusLogic_ParseDriverOptions(str);
}
__setup("BusLogic=", BusLogic_Setup);
Note that __setup() does nothing for modules, so the code that wishes to
process boot commandline and can be either a module or statically linked
must invoke its parsing function manually in the module initialisation
routine. This also means that it is possible to write code that
processes parameters when compiled as a module but not when it is static or
vice versa.