Programming

13373 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

[email protected]

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 [email protected] to c/[email protected]

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

[–] [email protected] 1 points 1 year ago

That's interesting, I don't have much contact with Apple's ecosystem.

Sounds similar to a setup that Linux allows, with the root filesystem on btrfs, making a snapshot of it and updating, then live switching kernels. But there is no firmware support to make the switch, so it relies on root having full access to everything.

The hypervisors approach seem like what Windows is doing, where Windows itself gets booted in a Hyper-X VM, allowing WSL2 and every other VM to run at "native" speed (since "native" itself is a VM), and in theory should allow booting a parallel updated Windows, then just switching VMs.

On Linux there is also a feature for live migrating VMs, which allows software to keep running while they're being migrated with just a minimum pause, so they could use something like that.