| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
the vm isn't getting an NMI for any real reason anyways, so I might as well
abuse it
|
|
|
|
|
|
|
|
|
|
|
|
not sure how that slipped by
|
|
|
|
|
|
|
|
|
|
not strictly necessary, but this should improve:
1. sleep performance
2. power efficiency when idle
|
|
After some consideration this seems like the most fitting way to handle
timekeeping. Directly, the syscall is only useful for keeping time within a
single process, but it is meant to be used for e.g. NTP clients, which will
provide the real time through the VFS.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
the rtl8139 mac wasn't being read correctly anyways, and the init stuff
wasn't revelant in ages.
the rest is relatively useful
|
|
|
|
This makes the side-effects more explicit, and feels less hacky than
`HANDLE_PROCFS`. I don't think accessing a handle alone should have
side-effects, even if it's a "special" one.
|
|
|
|
|
|
|
|
|
|
|
|
there's no real reason for bootstrap to be doing that, and this brings it closer
to only doing the elf loading
|
|
|
|
dash works now :^)))
|
|
|
|
|
|
I'm yet to write proper docs but the TL;DR is:
Mounting /proc/ creates a new pid namespace. You're still visible in the old
namespace with your old pid, but your children won't be. You see your own pid
as 1. Current pids of children will be preserved, pids will be allocated starting
from the highest one of your children.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
how.
|
