WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/hppa/dev?h=master 2021-03-11T11:16:54Z 2021-03-11T11:16:54Z jsg jsg@openbsd.org 2021-03-11T11:16:54Z urn:sha1:36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2 2021-02-23T04:44:30Z cheloha cheloha@openbsd.org 2021-02-23T04:44:30Z urn:sha1:8611d3cdb295683ad47c33036b86b471b2d09741 The timecounter struct is large and I think it may change in the future. Changing it later will be easier if we use C99-style initialization for all timecounter structs. It also makes reading the code a bit easier. For reasons I cannot explain, switching to C99-style initialization sometimes changes the hash of the resulting object file, even though the resulting struct should be the same. So there is a binary change here, but only sometimes. No behavior should change in either case. I can't compile-test this everywhere but I have been staring at the diff for days now and I'm relatively confident this will not break compilation. Fingers crossed. ok gnezdo@ 2020-07-06T13:33:05Z pirofti pirofti@openbsd.org 2020-07-06T13:33:05Z urn:sha1:d82e6535c6efd8305182f77041b2246ccfae1196 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@ 2020-05-29T04:42:23Z deraadt deraadt@openbsd.org 2020-05-29T04:42:23Z urn:sha1:c8f27247b9f5f282483daaddbfd1267ad73569c5 conversion steps). it only contains kernel prototypes for 4 interfaces, all of which legitimately belong in sys/systm.h, which are already included by all enqueue_randomness() users. 2020-05-01T19:56:11Z kettenis kettenis@openbsd.org 2020-05-01T19:56:11Z urn:sha1:78a860bb5a1c4c33fd41129870231c4771888573 amd64/arm64/armv7/i386/sparc64 and move it to the end of machdep.c. Rework the actual implementation for the MC14818 compatible RTC into something that can be used as a todr_handle just like on amd64. ok mpi@ 2020-03-06T01:45:32Z cheloha cheloha@openbsd.org 2020-03-06T01:45:32Z urn:sha1:b895fb73699709f2062b06abfc54cfd791a9f8ab Tested by kettenis@. ok kettenis@ 2019-10-12T15:53:24Z cheloha cheloha@openbsd.org 2019-10-12T15:53:24Z urn:sha1:448a8ce52070d79ca298e0927bfcfbe52203c488 2018-05-14T13:54:39Z kettenis kettenis@openbsd.org 2018-05-14T13:54:39Z urn:sha1:51f66ac76fe2119d6ac8316b4a09dbb260bff705 - dynamic allocation of interrupts for dino(4) and gsc(4) - only mention irq locators for devices which use interrupts. - for gsc(4), this actually postpones interrupt allocation until gsc(4) attaches, so asp(4)/lasi(4)/wax(4) won't route the interrupt yet, but the gsc(4) child will take care of this. - remove the irq locator for the drivers which do not need a fixed assignment. siop and moongoose could benefit from this but don't work at the moment so this is left as an exercize to future kernel hackers. A side effect from this is that we do not need multiple sti(4) attachment lines, so PCI sti(4) devices will now attach as sti0 rather than sti2. With this diff, multiple dino(4) devices attached to the same parent will use different interrupt sources, and more than two dino(4) devices can attach. Tested on 715/75 (old-gen using asp), 715/100/XC (new-gen using lasi), B132L+, B180L, C240, B2000, C3650. From miod@ 2018-02-19T08:59:52Z mpi mpi@openbsd.org 2018-02-19T08:59:52Z urn:sha1:3e6763994aeb80a553b07ba51b1db2c4725c5c88 The account flag `ASU' will no longer be set but that makes suser() mpsafe since it no longer mess with a per-process field. No objection from millert@, ok tedu@, bluhm@ 2016-08-19T20:48:36Z tedu tedu@openbsd.org 2016-08-19T20:48:36Z urn:sha1:82867933223e0fe00c89272afeefd9e114a29b2e (probably landed in dev because it has support for this viper thing, but i like consistency for the /dev/null parts.) ok kettenis