Searched refs:kernel (Results 1 – 10 of 10) sorted by relevance
1 # The xv6 kernel starts executing in this file. This file is linked with2 # the kernel C code, so it can refer to kernel symbols such as main().9 # Linux file system by copying kernel or kernelmemfs to /boot15 # set kernel='/boot/kernel'17 # multiboot ${kernel} ${kernel}
6 # kernel and CS == 35 in user space26 echo + symbol-file kernel\n27 symbol-file kernel
1 /* Simple linker script for the JOS kernel.10 /* Link the kernel at this address: "." means the current address */24 /* Include debugging information in kernel memory */42 * For the kernel mapping, we need the address at the beginning
93 xv6.img: bootblock kernel96 dd if=kernel of=xv6.img seek=1 conv=notrunc123 kernel: $(OBJS) entry.o entryother initcode kernel.ld target124 $(LD) $(LDFLAGS) -T kernel.ld -o kernel entry.o $(OBJS) -b binary initcode entryother125 $(OBJDUMP) -S kernel > kernel.asm126 $(OBJDUMP) -t kernel | sed '1,/SYMBOL TABLE/d; s/ .* / /; /^$$/d' > kernel.sym135 kernelmemfs: $(MEMFSOBJS) entry.o entryother initcode kernel.ld fs.img136 …$(LD) $(LDFLAGS) -T kernel.ld -o kernelmemfs entry.o $(MEMFSOBJS) -b binary initcode entryother f…193 initcode initcode.out kernel xv6.img fs.img kernelmemfs \
10 kernel loaded at 1 megabyte. stack same place that bootasm.S left it.17 no user area: no magic kernel stack mapping18 so no copying of kernel stack during fork19 though there is a kernel stack page for each process21 no kernel malloc(), just kalloc() for user core23 user pointers aren't valid in the kernel25 are interrupts turned on in the kernel? yes.43 oops, if kernel stack is in contiguous user phys mem, then moving45 kernel stack.
13 kernel
14 $p $($p -h | grep ' -[aipsf] ' | awk '{print $1}') -e kernel "$@"
80 kernel.ld
22 constructed at the top of cp's kernel stack. So tf
708 #load32bitOSImage: os=nullkernel, path=../kernel.img, iolog=../vga_io.log