Process Context and Interrupt Context

最新推荐文章于 2025-03-12 21:04:14 发布

RichardYSteven

最新推荐文章于 2025-03-12 21:04:14 发布

阅读量1.8k

点赞数

CC 4.0 BY-SA版权

分类专栏： Linux kernel 文章标签： user system go

本文链接：https://blog.youkuaiyun.com/RichardYSteven/article/details/4469196

Linux kernel 专栏收录该内容

49 篇文章

订阅专栏

本文探讨了操作系统内核如何通过进程上下文与中断上下文执行任务。内核为用户应用程序提供服务时运行在进程上下文中，并可以被抢占；而中断处理程序则总是运行到完成，不可抢占。中断上下文受限较多，例如不能睡眠、获取互斥锁或执行耗时任务等。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

The kernel accomplishes useful work using a combination of process contexts and interrupt contexts .

Kernel code that services system calls issued by user applications runs on behalf of the corresponding application
processes and is said to execute in process context .

Interrupt handlers, on the other hand, run asynchronously in interrupt context .

Processes contexts are not tied to any interrupt context and vice versa.

Kernel code running in process context is preemptible .

An interrupt context, however, always runs to completion and is not preemptible . Because of this, there are restrictions on what can be done from interrupt context.

Code executing from interrupt context cannot do the following:
Go to sleep or relinquish the processor
Acquire a mutex
Perform time-consuming tasks
Access user space virtual memory
Look at section "Interrupt Handing" in Chapter 4 for a full discussion of the interrupt context