Programming

13368 readers

2 users here now

All things programming and coding related. Subcommunity of Technology.

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 1 year ago

MODERATORS

alyaza@beehaw.org

Hexorg@beehaw.org

remington@beehaw.org

Why do we have two modes in cpu(user and kernel) since we still can still easily harm computer with userland programs? (lemm.ee)

submitted 1 year ago* (last edited 1 year ago) by SmoothSurfer@lemm.ee to c/programming@beehaw.org

23 comments fedilink hide all child comments

I have never dug into low level things like cpu architectures etc. and decided to give it a try when I learned about cpu.land.

I already was aware of the existence of user and kernel mode but while I was reading site it came to me that "I still can harm my system with userland programs so what does it mean to switch user mode for almost everything other than kernel and drivers?" also we still can do many things with syscalls, what is that stopping us(assuming we want to harm system of course) from damaging our system.

[edit1]: grammar mistakes

you are viewing a single comment's thread
view the rest of the comments

[–] bassdruminphonebox@beehaw.org 5 points 1 year ago (1 children)

I think one of the motivations for having separate modes like this, with (some) separate registers for each, is to reduce the time taken to switch contexts between modes. If they didn't have separate registers, the data in the user mode registers would have to be saved somewhere when making a switch into kernel mode, and then copied back again when switching back to user mode.

[–] jarfil@beehaw.org 2 points 1 year ago

There are no separate registers, every call to kernel mode takes extra time precisely because it has to save all the caller's registers, then restore them again before returning.

It involves even more registers than what's visible to the user, because the kernel also has to change the ones related to memory and device access permissions.