Linux-lab5：x86-64/arm64体系结构下进程切换的比较分析

context_switch

进程上下文切换的核心函数为`context_switch`，这一段代码位于内核中(目录为`kernel/sched/core.c`)，与体系结构无关。

```C
static inline void
context_switch(struct rq *rq, struct task_struct *prev,
	       struct task_struct *next)
{
	struct mm_struct *mm, *oldmm;

	prepare_task_switch(rq, prev, next);

	mm = next->mm;
	oldmm = prev->active_mm;
	/*
	 * For paravirt, this is coupled with an exit in switch_to to
	 * combine the page table reload and the switch backend into
	 * one hypercall.
	 */
	arch_start_context_switch(prev);

	if (!mm) {
		next->active_mm = oldmm;
		atomic_inc(&oldmm->mm_count);
		enter_lazy_tlb(oldmm, next);
	} else
		switch_mm(oldmm, mm, next);

	if (!prev->mm) {
		prev->active_mm = NULL;
		rq->prev_mm = oldmm;
	}
	/*
	 * Since the runqueue lock will be released by the next
	 * task (which is an invalid locking op but in the case
	 * of the scheduler it's an obvious special-case), so we
	 * do an early lockdep release here:
	 */
	spin_release(&rq->lock.dep_map, 1, _THIS_IP_);

	context_tracking_task_switch(prev, next);
	/* Here we just switch the register state and the stack. */
	switch_to(prev, next, prev);

	barrier();
	/*
	 * this_rq must be evaluated again because prev may have moved
	 * CPUs since it called schedule(), thus the 'rq' on its stack
	 * frame will be invalid.
	 */
	finish_task_switch(this_rq(), prev);
}
```

`context_switch()` 一共有三个传入参数，其中`rq`表示当前就绪队列，`struct rq`是一个成员非常多的结构体，描述了此CPU上所运行的所有进程，`prev`与`next`分别指向了是前序、后序进程的描述符。

`prepare_task_switch()`定义了特定体系结构的事前准备工作，大多数体系结构不需要其中的选项，该函数与`finish_task_switch()`是配套使用的。

`mm`表示`memory management`，当`mm`为`NULL`的时候，表示下一进程只是内核线程，它不会访问用户态地址空间，因此无需使当前TLB作废，于是在`atomic_inc()`增加前序`mm`的引用计数后，调用`惰性TLB`相关代码`enter_lazy_tlb()`；当`mm`非`NULL`，表示非内核线程，则需要切换虚拟地址空间，调用`switch_mm()`函数。

接下来，若前序线程是内核线程或正在退出的进程，即`prev->mm`非`NULL`，则其`active_mm`字段被置为`NULL`，整个运行队列的`prev_mm`也变为前序线程的