| created | 2019-10-19T09:37:30Z |
|---|---|
| begin | 2019-08-02T00:00:00Z |
| end | 2019-08-02T03:00:00Z |
| path | src/sys |
| commits | 1 |
| date | 2019-08-02T02:17:35Z | |||
|---|---|---|---|---|
| author | cheloha | |||
| files | src/sys/arch/sparc64/sparc64/db_interface.c | log | diff | annotate |
| src/sys/conf/param.c | log | diff | annotate | |
| src/sys/kern/kern_clock.c | log | diff | annotate | |
| src/sys/kern/kern_exec.c | log | diff | annotate | |
| src/sys/kern/kern_time.c | log | diff | annotate | |
| src/sys/sys/kernel.h | log | diff | annotate | |
| src/sys/sys/proc.h | log | diff | annotate | |
| message |
per-process itimers: itimerval -> itimerspec Loongson runs at 128hz. 128 doesn't divide evenly into a million, but it does divide evenly into a billion. So if we do the per-process itimer bookkeeping with itimerspec structs we can have error-free virtual itimers on loongson just as we do on most other platforms. This change doesn't fix the virtual itimer error alpha, as 1024 does not divide evenly into a billion. But this doesn't make the situation any worse, either. ok deraadt@ |
|||