wireguard-openbsd/sys/arch/amd64, branch jd/queueboostsWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/amd64?h=jd%2Fqueueboosts2020-06-22T12:27:54ZChange tsc_get_timecount return from uint to u_int per sys/timetc.h.2020-06-22T12:27:54Zpiroftipirofti@openbsd.org2020-06-22T12:27:54Zurn:sha1:b373bb1f2d041705cea84aa6125dc7f4c4ceae99
First brought up by naddy@ in the usertc thread, OK kettenis@.
fold the TSC value in fewer operations, same result; ok deraadt@2020-06-19T15:00:45Znaddynaddy@openbsd.org2020-06-19T15:00:45Zurn:sha1:ec4ed3a25fb7ac5b9c5a9ed6b8e4afed25159ea3pci_intr_establish_cpu() for establishing an interrupt no a specific cpu.2020-06-17T06:14:52Zdlgdlg@openbsd.org2020-06-17T06:14:52Zurn:sha1:15db3095c63a1a68b250e90fee88dec8bf7f637d
the cpu is specified by a struct cpu_info *, which should generally
come from an intrmap.
this is adapted from a diff that patrick@ sent round a few years
ago for a pci_intr_map_msix_cpuid, where you asked for an msi vector
on a specific cpu, and then called pci_intr_establish with the
handle you get. kettenis pointed out that it's hard on some archs
to carry cpu on a pci interrupt handle, so i tweaked it to turn it
into a pci_intr_establish_cpu instead.
jmatthew@ and i (but mostly jmatthew@ to be honest) have been
experimenting with this api on multiple archs and it is working out
well. i'm putting this diff in now on amd64 so people can kick the
tyres a bit.
tested with hacked up vmx(4), ix(4), and mcx(4)
make intr_barrier run sched_barrier on the cpu the interrupt pinned to.2020-06-16T23:35:10Zdlgdlg@openbsd.org2020-06-16T23:35:10Zurn:sha1:25a8a2823803742cd59c645fe1cc4232a405aa64
intr_barrier passed NULL to sched_barrier before this, which ends
up being the primary cpu. that's been mostly right until this point,
but is set to change.
Check rdrand for success and try up to ten times, as recommended by Intel.2020-06-15T19:25:16Znaddynaddy@openbsd.org2020-06-15T19:25:16Zurn:sha1:dd423e202033ea6a7a2ccc1435d3d86866bb60c5
Do the same for rdseed.
ok deraadt@
crank version number2020-06-14T16:06:25Zderaadtderaadt@openbsd.org2020-06-14T16:06:25Zurn:sha1:29c02c14e09366e368ddf37ede6a9862fbfa2d6basm versions of mdrandom() no longer needed2020-06-14T16:04:54Zderaadtderaadt@openbsd.org2020-06-14T16:04:54Zurn:sha1:0ddce9b0f2fc6f6888445b201113be717de0ac28rewrite mdrandom() in C. previously this XOR'd against rdrand if available,2020-06-14T16:00:08Zderaadtderaadt@openbsd.org2020-06-14T16:00:08Zurn:sha1:55f8664c3cb6c3d3b4f4fd806d3cc0a0106e6ba9
and alternatively XOR'd against TSC. now always run both sequences, and
also support rdseed as a third procedure.
ok kettenis naddy
update drm to linux 5.72020-06-08T04:47:57Zjsgjsg@openbsd.org2020-06-08T04:47:57Zurn:sha1:c349dbc7938c71a30e13c1be4acc1976165f4630
adds kernel support for
amdgpu: vega20, raven2, renoir, navi10, navi14
inteldrm: icelake, tigerlake
Thanks to the OpenBSD Foundation for sponsoring this work, kettenis@ for
helping, patrick@ for helping adapt rockchip drm and many developers for
testing.
let the random subsystem read the tsc for event "timestamps".2020-06-03T06:54:04Zdlgdlg@openbsd.org2020-06-03T06:54:04Zurn:sha1:b8f1c15c74bab3fdc46349a15171114bcc56e562