wireguard-openbsd/sys/arch/hppa, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/hppa?h=jd%2Fqueueboosts2020-06-14T20:29:13ZImplement cpu_rnd_messybits() as a read of the cycle counter register.2020-06-14T20:29:13Znaddynaddy@openbsd.org2020-06-14T20:29:13Zurn:sha1:2207d07413d2edf062148b9e5cdfa5b0a24c2bf2
ok dlg@ deraadt@
introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.2020-05-31T06:23:56Zdlgdlg@openbsd.org2020-05-31T06:23:56Zurn:sha1:01802d2cc63d886227ab3b39e923ff13cf516166
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.
dev/rndvar.h no longer has statistical interfaces (removed during various2020-05-29T04:42:23Zderaadtderaadt@openbsd.org2020-05-29T04:42:23Zurn: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.
Retire <machine/varargs.h>.2020-05-27T15:16:04Zvisavisa@openbsd.org2020-05-27T15:16:04Zurn:sha1:9df0f941a91e9f67cc4e63514cb174cb2a5783fd
Nothing uses the header anymore.
OK deraadt@ mpi@
increment version numbers, due to recent RB_GOODSEED and fchmod +T changes2020-05-26T14:00:40Zderaadtderaadt@openbsd.org2020-05-26T14:00:40Zurn:sha1:ed5a52b6bdf7c7f007d222e270b64343a6f85fc8iodcstrategy() maintains a cache for READ performance (tapes are supported2020-05-26T13:38:07Zderaadtderaadt@openbsd.org2020-05-26T13:38:07Zurn:sha1:6f64443005dfd4eb9f50513d9a9c5c08d0dc72a5
here, and alternatively would need to rewind). WRITE code exists, but was
always wrong -- it writes the cache-buffer to disk, rather than the provided
write-buffer. Copy the write-buffer into the cache, and invalidate the cache
completely so that future reads start from scratch.
Put setjmp+longjmp inside #ifdef DDB the only kernel-side user.2020-05-17T13:48:29Zderaadtderaadt@openbsd.org2020-05-17T13:48:29Zurn:sha1:be7994c5120c6f906321c4b77341c04fcaa65b03
This shrinks the ramdisks a tiny bit.
Make inittodr() and resettodr() MI.2020-05-16T14:44:44Zketteniskettenis@openbsd.org2020-05-16T14:44:44Zurn:sha1:5fcf2a4b8103efd7bc779ac85e97dbbe7542aaf4
ok deraadt@, mpi@, visa@
ok cheloha@ as well (would have preferred in new file for this code)
Initialize the timeval passed to todr_gettime() with the base time from2020-05-11T13:25:31Zketteniskettenis@openbsd.org2020-05-11T13:25:31Zurn:sha1:903250556290f4ea437844c80f12567b5d98bfdf
the file system such that implementations can use it to guess the right
century.
ok mpi@
Use the same inittodr()/resettodr() implementation as on2020-05-01T19:56:11Zketteniskettenis@openbsd.org2020-05-01T19:56:11Zurn: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@