wireguard-openbsd/lib/libc/thread, branch master WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/lib/libc/thread?h=master 2021-01-06T19:54:17Z Fix two issues related to thread private data in asr. 2021-01-06T19:54:17Z otto otto@openbsd.org 2021-01-06T19:54:17Z urn:sha1:a7244e9f7440612fd0e5c6899defce35f5a4c4ee - setting up asr in single thread mode and then starting threads using asr would lead to multiple threads sharing the same resolver. - destruction of a thread that has been using asr would leak data. Problem originally reported by Alexey Sokolov and Uli Schlachter. ok kettenis@ annoying whitespace 2020-10-12T22:06:51Z deraadt deraadt@openbsd.org 2020-10-12T22:06:51Z urn:sha1:ce775b4f526bf06da26b3a79c6d7fe719b89f7b8 Add support for timeconting in userland. 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@ Instead of opting in to futexes on archs with atomics opt out on archs 2020-02-06T03:13:45Z jsg jsg@openbsd.org 2020-02-06T03:13:45Z urn:sha1:2ee00db36bd4c31e23829424e9f44f4dbb4646f4 without atomics, a smaller list. ok mpi@ visa@ Kill unused _wait() function. 2019-10-21T10:04:19Z mpi mpi@openbsd.org 2019-10-21T10:04:19Z urn:sha1:7268b626954e8800e2f2bb9eb6f527afbf37ff01 ok visa@ KNF. 2019-02-13T13:09:32Z mpi mpi@openbsd.org 2019-02-13T13:09:32Z urn:sha1:47f3b7d8926660a01a14e2ea3408f97d45323072 Pointed out by pirofti@ while reviewing my rwlock impl. based on this one. Remove unused <assert.h> header. 2019-01-29T17:41:14Z mpi mpi@openbsd.org 2019-01-29T17:41:14Z urn:sha1:f98b88ec7828e948aebf32f0586bc72e5f1fec18 There's no point in asserting that a pointer is not NULL before 2019-01-29T17:40:26Z mpi mpi@openbsd.org 2019-01-29T17:40:26Z urn:sha1:f3cfced65d8763697064247625744e9c5b07f080 dereferencing it. ok kettenis@, visa@ Make the "not my pool" searching loop a tiny bit smarter, while 2019-01-10T18:45:33Z otto otto@openbsd.org 2019-01-10T18:45:33Z urn:sha1:fa2b64111b6ceb302725eb7311a0f7b9fbddf988 making the number of pools variable. Do not document the malloc conf settings atm, don't know yet if they will stay. Thanks to all the testers. ok deraadt@ Switch alpha to futex(2) based condvars, mutexes and semaphores. 2018-10-21T17:07:24Z visa visa@openbsd.org 2018-10-21T17:07:24Z urn:sha1:2b819b9469dd1b5852b324ae10fcffed47a792b5 From Brad, tested by Miod, OK kettenis@