wireguard-openbsd/sys/arch/amd64/stand, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64/stand?h=jd%2Fqueueboosts 2020-06-19T15:00:45Z fold the TSC value in fewer operations, same result; ok deraadt@ 2020-06-19T15:00:45Z naddy naddy@openbsd.org 2020-06-19T15:00:45Z urn:sha1:ec4ed3a25fb7ac5b9c5a9ed6b8e4afed25159ea3 Check rdrand for success and try up to ten times, as recommended by Intel. 2020-06-15T19:25:16Z naddy naddy@openbsd.org 2020-06-15T19:25:16Z urn:sha1:dd423e202033ea6a7a2ccc1435d3d86866bb60c5 Do the same for rdseed. ok deraadt@ crank version number 2020-06-14T16:06:25Z deraadt deraadt@openbsd.org 2020-06-14T16:06:25Z urn:sha1:29c02c14e09366e368ddf37ede6a9862fbfa2d6b asm versions of mdrandom() no longer needed 2020-06-14T16:04:54Z deraadt deraadt@openbsd.org 2020-06-14T16:04:54Z urn:sha1:0ddce9b0f2fc6f6888445b201113be717de0ac28 rewrite mdrandom() in C. previously this XOR'd against rdrand if available, 2020-06-14T16:00:08Z deraadt deraadt@openbsd.org 2020-06-14T16:00:08Z urn:sha1:55f8664c3cb6c3d3b4f4fd806d3cc0a0106e6ba9 and alternatively XOR'd against TSC. now always run both sequences, and also support rdseed as a third procedure. ok kettenis naddy increment version numbers, due to recent RB_GOODSEED and fchmod +T changes 2020-05-26T14:00:40Z deraadt deraadt@openbsd.org 2020-05-26T14:00:40Z urn:sha1:ed5a52b6bdf7c7f007d222e270b64343a6f85fc8 Adjust mdrandom() to also return 0 for success, -1 for failure 2020-05-25T14:58:01Z deraadt deraadt@openbsd.org 2020-05-25T14:58:01Z urn:sha1:fd17f4d1e659a22fc90bdcd3abda1e98f1bc406f Adjust fwrandom() to return 0 for sucess, -1 for failure 2020-05-25T14:53:57Z deraadt deraadt@openbsd.org 2020-05-25T14:53:57Z urn:sha1:d4fa8acb0d6af3b6ddbd07c22e37180c5e52477f Make efi_device_path_depth() return the full device path depth if we don't 2020-03-22T14:59:11Z kettenis kettenis@openbsd.org 2020-03-22T14:59:11Z urn:sha1:d64e7de5becbe0ba830e2fc56c82029052ec5766 find a media device path node. Fixes booting OpenBSD on some older U-Boot versions that are in wide circulation such as 2017.09 and 2017.11. ok patrick@ Recommit, now that we found out how to fix the BIOS related issues: go 2020-03-09T06:16:56Z otto otto@openbsd.org 2020-03-09T06:16:56Z urn:sha1:fe786928396429aa72273b879445e54a2d9bf75e back to a 4 byte add instruction. We do not know *why* though, so if somebody likes a challenge... Lots of help from semarie@ who has a few systems showing the issue. ok deraadt@