FONT SIZE : AAA
System Call Interface
A system call is an interaction between an application in the user space and the required service provided by the kernel. The SCI provides this link between the boundary of the user space and kernel space, where direct calls are not possible. The implementation of a
Linux system call can vary depending on the processor architecture. Figure 23.2 represents one such simplified approach based on processor interrupts[1].
• All system calls are multiplexed through a single kernel entry point, identifiable by a register as specified in and loaded from the C library.
• A software interrupt is triggered and the interrupt handler executes the system_call function.
• The identifying register indexes the system_call_table to trigger the correct system call via the SCI.
• Returning from the system call, there is a transition back to the user space where execution continues in the C library and original user application.
System calls therefore provide a level of abstraction between the programs in the user space and the kernel itself. This also gives greater consistency to the interactions between all user applications and the kernel code.
Manufacturer:Xilinx
Product Categories:
Lifecycle:Any -
RoHS:
Manufacturer:Xilinx
Product Categories: CPLDs
Lifecycle:Active Active
RoHS: No RoHS
Manufacturer:Xilinx
Product Categories: Embedded - CPLDs (Complex Programmable Logic Devices)
Lifecycle:Active Active
RoHS:
Manufacturer:Xilinx
Product Categories: Embedded - CPLDs (Complex Programmable Logic Devices)
Lifecycle:Active Active
RoHS:
Manufacturer:Xilinx
Product Categories: FPGAs
Lifecycle:Obsolete -
RoHS: -
Support
