flâneur

Syscalls | Pintos Documentation

cs162.org · 272 words · saved by 1 readers

One way that the operating system can regain control from a user program is external interrupts from timers and I/O devices. These are “external” interrupts, because they are caused by entities outside the CPU. The operating system also deals with software exceptions, which are events that occur in program code. These can be errors such as a page fault or division by zero. Exceptions are also the means by which a user program can request system calls (syscalls) (i.e. services) from the operating system. In the 80x86 architecture, the int instruction is the most commonly used means for invoking system calls. This instruction is handled in the same way as other software exceptions. In Pintos, user programs invoke int $0x30 to make a system call. The system call number and any additional arguments are expected to be pushed on the stack in the normal fashion before invoking the interrupt (see 80x86 Calling Convention). Thus, when the system call handler syscall_handler gets control, the sy

Syscalls | Pintos Documentation Skip to main content Menu Expand (external link) Document Search Copy Copied Pintos Documentation Syscalls One way that the operating system can regain control from a user program is external interrupts from timers and I/O devices. These are “external” interrupts, because they are caused by entities outside the CPU. The operating system also deals with software exceptions , which are events that occur in program code. These can be errors such as a page fault or division by zero. Exceptions are also the means by which a user program can request system calls (sysc

related reading