analyzing the System_call interrupt processing processShahuzy Original works reproduced please specify the source + "Linux kernel analysis" MOOC course http://mooc.study.163.com/course/USTC-1000029000 One, The experiment content uses the GDB trace to analyze a system call kernel function (selected last week), starting from System_call to the end of the Iret process, and drawing a concise and accurate flowchart.second, the experimental process first into the experimental building environment, into the linuxkernel Folders, updatingmenu file.
Then go to the Menu folder, test.c file to add functions.
The function is added at the place, the operation is as follows.
The make Rootfs is then started, but a run error has occurred and two modifications have not been made (pending modification)
Iii. Summary of the experiment
Procedure for system calls: Typically, a set of subroutines (procedures) for implementing various system functions are set up in the core of the OS and are provided to the user for invocation. Whenever a user needs an OS to provide some kind of service in a program, a system invoke command is used to invoke the system procedure. It is generally run in a system state, accessed by an interrupt, and usually needs to be re-dispatched (and therefore not necessarily returned directly to the calling procedure). The process of Linux system invocation is very simple, it is interrupted by the 0x80 to enter the system call portal, by using the system call table to save the system Call service function entry address to implement.
Analyzing the System_call interrupt processing process
