wireguard-openbsd/sys/arch/mips64/include, branch master

spelling

2021-03-11T11:16:54Z

Userland timecounter implementation for octeon

2020-07-18T08:37:43Z

OK naddy@; no objections from kettenis@

Synchronize each core's CP0 cycle counter using the IO clock counter.

2020-07-11T15:18:08Z

This makes the cycle counter usable as timecounter on multiprocessor machines. Idea from Linux. Tested on CN5020, CN6120, CN7130 and CN7360. Looks reasonable to kettenis@

do not need these versions of timetc.h

2020-07-08T14:45:15Z

Add support for timeconting in userland.

2020-07-06T13:33:05Z

This diff exposes parts of clock_gettime(2) and gettimeofday(2) to userland via libc eliberating processes from the need for a context switch everytime they want to count the passage of time. If a timecounter clock can be exposed to userland than it needs to set its tc_user member to a non-zero value. Tested with one or multiple counters per architecture. The timing data is shared through a pointer found in the new ELF auxiliary vector AUX_openbsd_timekeep containing timehands information that is frequently updated by the kernel. Timing differences between the last kernel update and the current time are adjusted in userland by the tc_get_timecount() function inside the MD usertc.c file. This permits a much more responsive environment, quite visible in browsers, office programs and gaming (apparently one is are able to fly in Minecraft now). Tested by robert@, sthen@, naddy@, kmos@, phessler@, and many others! OK from at least kettenis@, cheloha@, naddy@, sthen@

Remove obsolete header. Nowadays the vararg

2020-06-30T15:41:55Z

functionality is provided by using compiler builtins. Tested in a ports bulk build on amd64 by naddy@ OK naddy@ mpi@

introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.

2020-05-31T06:23:56Z

rnd.c uses nanotime to get access to some bits that change quickly between events that it can mix into the entropy pool. it doesn't use nanotime to get a monotonically increasing set or ordered and accurate timestamps, it just wants something with bits that change. there's been discussions for years about letting rnd use a clock that's super fast to read, but not necessarily accurate, but it wasn't until recently that i figured out it wasn't interested in time at all, so things like keeping a fast clock coherent between cpu cores or correct according to ntp is unecessary. this means we can just let rnd read the cycle counters on cpus and things will be fine. cpus with cycle counters that vary in their speed and arent kept consistent between cores may even be desirable in this context. so this is the first step in converting rnd.c to reading cycle counter. it copies the nanotime backend to each arch, and they can replace it with something MD as a second step later on. djm@ suggested rnd_messybytes, but we landed on cpu_rnd_messybits. thanks to visa for his eyes. ok deraadt@ visa@ deraadt@ says he will help handle any MD fallout that occurs.

Retire .

2020-05-27T15:16:04Z

Nothing uses the header anymore. OK deraadt@ mpi@

Convert db_addr_t -> vaddr_t but leave the typedef for now.

2019-11-07T14:44:52Z

Substitute boolean_t/TRUE/FALSE by int/1/0.

2019-11-07T11:04:21Z

ok dlg@, jasper@