0xAX/linux-insides

SYSCALL - multitasking & Interruput event

Open

#493 建立於 2017年7月16日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)Python (29,341 star) (3,301 fork)batch import
help wanted

描述

Dear OxAX , Thanks for your efforts for writing "Linux Inside" . It has cleared most of my doubts. I request you to please elaborate few technical doubts about System call .

  1. System call in multitasking environment : a. What will happen if higher priority task need system resources by SYSCALL but already lower priority task's SYSCALL in running ( kernel code is executing ) ?

b. During one system call multitasking / multi threading is still possible or only one thread will have access to SYSCALL ?

  1. System call during External / Peripheral interrupt : a. what will happen if external interrupt or higher priority pheripheral interrupt triggers while processing SYSCALL ?

Request you to please reply on this & if possible please add explanation in "Linux Inside"

Regards, Gaurav

貢獻者指南

技術棧
c
領域
documentation
議題類型
documentation
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
over 1 week
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Linux kernel basicssystem call mechanismsinterrupt handling
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
15
研究方向
Investigate the Linux kernel syscall entry points (e.g., arch/x86/kernel/entry 64.S) and scheduling mechanism (kernel/sched/core.c) to explain how system calls interact with multitasking. Also analyze interrupt handling code (kernel/irq/) to describe what happens when an interrupt occurs during a syscall. Consider adding a new section to the linux insides book covering these scenarios.