π§ππ ππ’π‘π‘πππ§ππ’π‘ πππ§πͺπππ‘ π¨π¦ππ₯ π£π₯π’ππ₯ππ π¦ ππ‘π π’π¦ πππ₯π‘ππ
The relation between the user mode and the OS kernel is a heavily guarded process. User mode is basically where the user program runs and does the basic things with limited privileges and kernel mo...

Source: DEV Community
The relation between the user mode and the OS kernel is a heavily guarded process. User mode is basically where the user program runs and does the basic things with limited privileges and kernel mode is unrestricted access to the whole system and hardware. By default, user programs canβt enter kernel mode to ensure the safety of the system. π¦π¬π¦π§ππ ππππ - π§ππ ππ₯ππππ As user programs are not directly given access to the Kernel. There is a bridge that is called sytem call where the OS is the guard who decides who gets to enter and where to go inside the kernel. System call is just an abstract concept, behind the scene this is just a instruction called βTrapβ (syscall). π§π₯ππ£ ππππ ππ¬πππ: π§ππ π₯ππ€π¨ππ¦π§: If a program wants to do something it does not have the privilege. It calls a standard library function to make this request. π§ππ π§π₯ππ£: Inside the library function, there is a machine instruction called trap or syscall. Which is executed. π¦ππ©οΏ½