wireguard-openbsd/sys/arch/mips64, branch masterWireGuard implementation for the OpenBSD kernelhttps://git.zx2c4.com/wireguard-openbsd/atom/sys/arch/mips64?h=master2021-03-11T11:16:54Zspelling2021-03-11T11:16:54Zjsgjsg@openbsd.org2021-03-11T11:16:54Zurn:sha1:36fd90dcf1acf2ddb4ef5dbabe5313b3a8d46ee2Update clock interrupt count atomically.2021-03-04T15:38:06Zvisavisa@openbsd.org2021-03-04T15:38:06Zurn:sha1:ce81117b77a368029b0dbf6f4fdb5b1037e4a2cb
This avoids errors that can arise when multiple cores update the
variable at the same time.
timecounting: use C99-style initialization for all timecounter structs2021-02-23T04:44:30Zchelohacheloha@openbsd.org2021-02-23T04:44:30Zurn:sha1:8611d3cdb295683ad47c33036b86b471b2d09741
The timecounter struct is large and I think it may change in the
future. Changing it later will be easier if we use C99-style
initialization for all timecounter structs. It also makes reading the
code a bit easier.
For reasons I cannot explain, switching to C99-style initialization
sometimes changes the hash of the resulting object file, even though
the resulting struct should be the same. So there is a binary change
here, but only sometimes. No behavior should change in either case.
I can't compile-test this everywhere but I have been staring at the
diff for days now and I'm relatively confident this will not break
compilation. Fingers crossed.
ok gnezdo@
Leave out gp initialization from kernel entry on mips642021-02-11T14:44:13Zvisavisa@openbsd.org2021-02-11T14:44:13Zurn:sha1:5b34c8b171a4ddaff75b436d37df77a3c2241a24
On OpenBSD/mips64, the kernel is compiled with -mno-abicalls. This
disables gp-relative addressing and essentially makes gp a spare
register in the kernel. Hence it is unnecessary to initialize gp when
entering the kernel. The _gp symbol is not needed either.
Suggested by miod@
kernel, sysctl(8): remove dead variable: tickadj2021-01-13T16:28:49Zchelohacheloha@openbsd.org2021-01-13T16:28:49Zurn:sha1:9589ba9d8c337eade22f8e39fd77554e71d63034
The global "tickadj" variable is a remnant of the old NTP adjustment
code we used in the kernel before the current timecounter subsystem
was imported from FreeBSD circa 2004 or 2005.
Fifteen years hence it is completely vestigial and we can remove it.
We probably should have removed it long ago but I guess it slipped
through the cracks. FreeBSD removed it in 2002:
https://cgit.freebsd.org/src/commit/?id=e1d970f1811e5e1e9c912c032acdcec6521b2a6d
NetBSD and DragonflyBSD can probably remove it, too.
We export tickadj via the kern.clockrate sysctl(2), so update sysctl.2
and sysctl(8) accordingly. Hypothetically this change could break
someone's sysctl(8) parsing script. I don't think that's very likely.
ok mvs@
Initialize mips64 pmap pool using IPL_VM.2020-12-24T10:10:49Zvisavisa@openbsd.org2020-12-24T10:10:49Zurn:sha1:2f0334fab0dec087739f5ea65d0f6997a14bc31a
This moves the pmap closer to MP-safety. A similar change has already
been made on some other architectures.
In case of failure, call sigexit() from trapsignal instead of sensig().2020-11-08T20:37:21Zmpimpi@openbsd.org2020-11-08T20:37:21Zurn:sha1:1e286331f8cc3115cda0264eb0f546f9bd24d75a
Simplify MD code and reduce the amount of recursion into the signal code
which helps when dealing with locks.
ok cheloha@, deraadt@
uvm_grow() doesn't need KERNEL_LOCK anymore, and onfault never did.2020-10-22T13:41:49Zderaadtderaadt@openbsd.org2020-10-22T13:41:49Zurn:sha1:2d10d447aec306a7010206856b305bfd49ebb4e4
minor refactorings to narrow KERNEL_LOCK just around uvm_fault()
ok kettenis
uvm_grow() now does the vm_maxsaddr check (before locking), so callers don't2020-10-21T17:54:33Zderaadtderaadt@openbsd.org2020-10-21T17:54:33Zurn:sha1:3e784f98c8c2fbd7836eaebff22d9511f3884fff
need to do it
ok kettenis
mips64 has same bug as arm64: copyout(9), copyinstr(9) and2020-10-21T15:50:00Zderaadtderaadt@openbsd.org2020-10-21T15:50:00Zurn:sha1:7173b8f0fdfcb24b7919b84db09ebd6e4c993dc9
copyoutstr(9) should bail out properly if they are called with
a length of 0.
ok visa