1.在ubantu配置实验环境:
wget https://raw.github.com/mengning/mykernel/master/mykernel-2.0_for_linux-5.4.34.patch(直接从GitHub拿,使用wget有可能失败) sudo apt install axel axel -n 20 https://mirrors.edge.kernel.org/pub/linux/kernel/v5.x/linux-5.4.34.tar.xz xz -d linux-5.4.34.tar.xz tar -xvf linux-5.4.34.tar cd linux-5.4.34 patch -p1 < ../mykernel-2.0_for_linux-5.4.34.patch sudo apt install build-essential libncurses-dev bison flex libssl-dev libelf-dev
make defconfig # Default configuration is based on 'x86_64_defconfig'
make -j$(nproc) sudo apt install qemu # install QEMU qemu-system-x86_64 -kernel arch/x86/boot/bzImage
当出现以下窗口就配置成功了:
2.基于mykernel 2.0编写一个操作系统内核,(参照https://github.com/mengning/mykernel 提供的范例代码)
参考 PPT 以及老师上课的讲解,在 mykernel 文件夹中添加 mypcb.h (进程描述头文件),并修改 mymain.c 和 myinterrupt.c 中的代码,所以我们需要在mymain.c的基础上完成PCB和进程管理的代码,在myinterrupt.c的基础上完成进程切换代码,就可以完成一个可运行的OS kernel。
1.将GitHub的mypch.h放进虚拟机:
2. mypcb.h代码及其注释:
#define MAX_TASK_NUM 4 #define KERNEL_STACK_SIZE 1024*2 /* CPU-specific state of this task */ struct Thread { unsigned long ip; unsigned long sp; }; typedef struct PCB{ int pid;//线程号 volatile long state; /* -1 unrunnable, 0 runnable, >0 stopped *///进程状态 -1表示就绪态,0表示运行态,大于0表示阻塞态 unsigned long stack[KERNEL_STACK_SIZE]; //进程堆栈 /* CPU-specific state of this task */ struct Thread thread; //当前正在执行的线程信息 unsigned long task_entry; //进程入口函数 struct PCB *next;//指向下一个PCB,系统中所有的PCB是以链表的形式组织起来的。 }tPCB; void my_schedule(void);
3.修改mymain.c中的my_start_kernel函数,并在mymain.c中实现了my_process函数,用来作为进程的代码模拟一个个进程,时间片轮转调度。
#include "mypcb.h" tPCB task[MAX_TASK_NUM]; tPCB * my_current_task = NULL; volatile int my_need_sched = 0; void my_process(void); void __init my_start_kernel(void) { int pid = 0; int i; /* Initialize process 0*/ task[pid].pid = pid; task[pid].state = 0;/* -1 unrunnable, 0 runnable, >0 stopped */ task[pid].task_entry = task[pid].thread.ip = (unsigned long)my_process; task[pid].thread.sp = (unsigned long)&task[pid].stack[KERNEL_STACK_SIZE-1]; task[pid].next = &task[pid]; /*fork more process */ for(i=1;i) { memcpy(&task[i],&task[0],sizeof(tPCB)); task[i].pid = i; task[i].state = -1; task[i].thread.sp = (unsigned long)&task[i].stack[KERNEL_STACK_SIZE-1]; task[i].next = task[i-1].next; task[i-1].next = &task[i]; } /* start process 0 by task[0] */ pid = 0; my_current_task = &task[pid]; asm volatile( "movq %1,%%rsp\n\t" /* set task[pid].thread.sp to rsp */ "pushq %1\n\t" /* push rbp */ "pushq %0\n\t" /* push task[pid].thread.ip */ "ret\n\t" /* pop task[pid].thread.ip to rip */ : : "c" (task[pid].thread.ip),"d" (task[pid].thread.sp) /* input c or d mean %ecx/%edx*/ ); } void my_process(void) { int i = 0; while(1) { i++; if(i%10000000 == 0) { printk(KERN_NOTICE "this is process %d -\n",my_current_task->pid); if(my_need_sched == 1) { my_need_sched = 0; my_schedule(); } printk(KERN_NOTICE "this is process %d +\n",my_current_task->pid); } } }
该my_start_kernel函数嵌入一个关键的汇编代码:
asm volatile( "movq %1,%%rsp\n\t" /* set task[pid].thread.sp to rsp */ // 将进程原堆栈栈顶的地址存⼊RSP寄存器 "pushq %1\n\t" /* push rbp */ //将当前RBP寄存器值压栈 "pushq %0\n\t" /* push task[pid].thread.ip */ //将当前进程的RIP压栈 "ret\n\t" /* pop task[pid].thread.ip to rip */ // ret命令正好可以让压栈的进程RIP保存到RIP寄存器中 : : "c" (task[pid].thread.ip),"d" (task[pid].thread.sp) /* input c or d mean %ecx/%edx*/ );
(4)对myinterrupt.c的修改,my_timer_handler用来记录时间片,时间片消耗完之后完成调度。并在该文件中完成,my_schedule(void)函数的实现;
#include "mypcb.h" extern tPCB task[MAX_TASK_NUM]; extern tPCB * my_current_task; extern volatile int my_need_sched; volatile int time_count = 0; /* * Called by timer interrupt. */ void my_timer_handler(void) { if(time_count%1000 == 0 && my_need_sched != 1) { printk(KERN_NOTICE ">>>my_timer_handler here<<<\n"); my_need_sched = 1; } time_count ++ ; return; } void my_schedule(void) { tPCB * next; tPCB * prev; if(my_current_task == NULL || my_current_task->next == NULL) { return; } printk(KERN_NOTICE ">>>my_schedule<<<\n"); /* schedule */ next = my_current_task->next; prev = my_current_task; if(next->state == 0)/* -1 unrunnable, 0 runnable, >0 stopped */ { my_current_task = next; printk(KERN_NOTICE ">>>switch %d to %d<<<\n",prev->pid,next->pid); /* switch to next process */ asm volatile( "pushq %%rbp\n\t" /* save rbp of prev */ "movq %%rsp,%0\n\t" /* save rsp of prev */ "movq %2,%%rsp\n\t" /* restore rsp of next */ "movq $1f,%1\n\t" /* save rip of prev */ "pushq %3\n\t" "ret\n\t" /* restore rip of next */ "1:\t" /* next process start here */ "popq %%rbp\n\t" : "=m" (prev->thread.sp),"=m" (prev->thread.ip) : "m" (next->thread.sp),"m" (next->thread.ip) ); } return; }
然后是myinterrupt.c,里面的my_timer_handler 函数会被内核周期性的调用,每调用1000次,就去将全局变量my_need_sched的值修改为1,my_start_kernel中的while循环发现my_need_sched值变为1后,就进行进程的调度,完成进程的切换,如此往复。
asm volatile( "pushq %%rbp\n\t" /* save rbp of prev */ "movq %%rsp,%0\n\t" /* save rsp of prev */ "movq %2,%%rsp\n\t" /* restore rsp of next */ "movq $1f,%1\n\t" /* save rip of prev */ "pushq %3\n\t" "ret\n\t" /* restore rip of next */ "1:\t" /* next process start here */ "popq %%rbp\n\t" : "=m" (prev->thread.sp),"=m" (prev->thread.ip) : "m" (next->thread.sp),"m" (next->thread.ip) );
pushq %%rbp: 保存prev进程(本例中指进程0)当前RBP寄存器的值到堆栈;
movq %%rsp,%0 :保存prev进程(本例中指进程0)当前RSP寄存器的值到prev->thread.sp,这时RSP寄存器指向进程的栈顶地址,实际上就是将prev进程的栈顶地址保存;
movq %2,%%rsp: 将next进程的栈顶地址next->thread.sp放⼊RSP寄存器,完成了进程0和进程1的堆栈切换。
movq $1f,%1 :保存prev进程当前RIP寄存器值到prev->thread.ip,这⾥$1f是指标号1。
pushq %3 :把即将执⾏的next进程的指令地址next->thread.ip⼊栈,这时的next->thread.ip可能是进程1的起点my_process(void)函数,也可能是$1f(标号1)。第⼀次被执⾏从头开始为进程1的起点my_process(void)函数,其余的情况均为$1f(标号1),因为next进程如果之前运⾏过那么它就⼀定曾经也作为prev进程被进程切换过。
ret :就是将压⼊栈中的next->thread.ip放⼊RIP寄存器,为什么不直接放⼊RIP寄存器呢?因为程序不能直接使⽤RIP寄存器,只能通过call、ret等指令间接改变RIP寄存器。
1: 标号1是⼀个特殊的地址位置,该位置的地址是$1f。
popq %%rbp :将next进程堆栈基地址从堆栈中恢复到RBP寄存器中。
自此,就完成了进程0与进程1的切换,其他两个相邻进程的切换过程也和这个相同。
5.重新make并运行mykernel