wireguard-openbsd/sys/arch/hppa/dev/clock.c, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/hppa/dev/clock.c?h=jd%2Fqueueboosts 2020-05-01T19:56:11Z Use the same inittodr()/resettodr() implementation as on 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@ It's been a quarter century: we can assume volatile is present with that name. 2014-03-29T18:09:28Z guenther guenther@openbsd.org 2014-03-29T18:09:28Z urn:sha1:2df76cc2a0aee2cb2166e3799b7bb5c3f883f83d ok dlg@ mpi@ deraadt@ Check in resettodr() if inittodr() has been called, otherwise we end up 2011-01-09T19:37:51Z jasper jasper@openbsd.org 2011-01-09T19:37:51Z urn:sha1:8ac7a9e3a954912293f0ed14795ae39909578bc3 resetting the clock when we don't need to. Found out with booting hppa64 kernels, and the problem also exists on hppa when booting with '-a' and hitting 'exit' when asked for the root filesystem. help & ok jsing@ also ok kettenis@ (who suggested naming the variable like amd64/i386 to prevent creating yet another variant of this code) - remove unused headers wrapped in #if defined(DDB) 2011-01-05T16:30:50Z jasper jasper@openbsd.org 2011-01-05T16:30:50Z urn:sha1:b024cdb98bc13c912c498e63d349ac6be2073384 ok jsing@ kettenis@ Move setting cpu_hzticks to the clock initialization function, like 2011-01-01T19:00:56Z jasper jasper@openbsd.org 2011-01-01T19:00:56Z urn:sha1:ea1135a80820940ed0533cfb0618d2b51912fba4 other ports (e.g. hppa64) do. ok jsing@ kettenis@ ANSIfy 2010-08-01T09:01:45Z kettenis kettenis@openbsd.org 2010-08-01T09:01:45Z urn:sha1:34f005a26d2bc8b34c4d4735497c525183ef0f41 Store hardware timer information per CPU. 2010-04-29T12:35:14Z jsing jsing@openbsd.org 2010-04-29T12:35:14Z urn:sha1:03854a774a53a43260b850e75e890d19f7899cd5 ok kettenis@ Make sure than cpu_hardclock() never sets a ``next interrupt value'' which has 2009-02-08T18:33:28Z miod miod@openbsd.org 2009-02-08T18:33:28Z urn:sha1:e60948ef71950afa841ba1f0ea49b82410d64ac2 already been hit by the running timer; this happens very often on oosiop-based machines, due to these machines being among the slowest hppa, and oosiop being interrupt greedy. Unfortunately, when this happened, one had to wait for the timer to wrap, which would take up to 128 seconds on the 33MHz machines. Also, invoke hardclock() as many times as necessary if it turns out that we had to delay the interrupt 1/hz seconds to avoid the aforementioned wrap problem. With help from kettenis@; ok kettenis@ Move hppa to __HAVE_TIMECOUNTERS. 2007-07-22T19:24:45Z kettenis kettenis@openbsd.org 2007-07-22T19:24:45Z urn:sha1:51f3178a045d5bedd738b81868cff8bebbd38cbe update copyright; miod@ is fine w/ files where he holds it too 2004-04-07T18:24:19Z mickey mickey@openbsd.org 2004-04-07T18:24:19Z urn:sha1:fef2e65f60a6303ee55b7aa64339bed537c525b9