summaryrefslogtreecommitdiffstats
path: root/sys/arch/alpha (follow)
Commit message (Collapse)AuthorAgeFilesLines
* spellingjsg2021-03-112-4/+4
|
* timecounting: use C99-style initialization for all timecounter structscheloha2021-02-231-2/+9
| | | | | | | | | | | | | | | | | | 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@
* Add uhidpp(4), a driver for Logitech HID++ devices. Currently limited toanton2021-02-041-1/+2
| | | | | | | | | exposing battery sensors for HID++ 2.0 devices. Most of the code is derived from the hid-logitech-hidpp Linux driver. Thanks to Ville Valkonen <weezeldinga at gmail dot com> for testing. ok mglocker@
* repair declerations to satisfy -fno-commonderaadt2021-01-293-19/+4
| | | | ok kettenis
* Again allow COPTS= to come from the environment again, and don't lose thederaadt2021-01-281-4/+4
| | | | | SMALL_KERNEL specific variations. ok espie jsg
* introduce ujoy(4), a restricted subset of uhid(4) for gamecontrollers.thfr2021-01-232-2/+5
| | | | | | | | This includes ujoy_hid_is_collection() to work around limitations of hid_is_collection() until this can be combined without fallout. input, testing with 8bitdo controller, and ok brynet@ PS4 controller testing, fix for hid_is_collection, and ok mglocker@
* Use daddr_t and not daddr32_t in boot media.krw2020-12-092-5/+5
| | | | | | | | | | At a minimum, amd64/i386 should now boot from 4TB GPT formatted disks. More daddr32_t terminations with extreme prejudice to follow. Tested by various, in snaps for a few days. ok deraadt@
* In case of failure, call sigexit() from trapsignal instead of sensig().mpi2020-11-081-12/+7
| | | | | | | Simplify MD code and reduce the amount of recursion into the signal code which helps when dealing with locks. ok cheloha@, deraadt@
* multiple reads of pmap_emulate_reference() don't show any reason for itderaadt2020-11-071-7/+3
| | | | to need KERNE_LOCK. Been testing this for about 3 weeks.
* observed by miod, a kernel unlock missed in last commitderaadt2020-10-271-3/+5
|
* As done with other architectures, narrow the KERNEL_LOCK around uvm_fault()deraadt2020-10-251-4/+5
| | | | as best we can.
* uvm_grow() doesn't need KERNEL_LOCK anymore, and onfault never did.deraadt2020-10-221-7/+4
| | | | | minor refactorings to narrow KERNEL_LOCK just around uvm_fault() ok kettenis
* (same as sh/sh/trap.c)deraadt2020-10-211-7/+3
| | | | | | The condition around uvm_grow() can be simplified, as the error result adjustment is effectively a dead store ok kettenis
* whitespacederaadt2020-10-211-19/+19
|
* uvm_grow() now does the vm_maxsaddr check (before locking), so callers don'tderaadt2020-10-211-3/+2
| | | | | need to do it ok kettenis
* alpha, loongson, sh, sparc64: recompute tick, tick_nsec when hz(9) is resetcheloha2020-10-201-1/+3
| | | | | | | | | | | | | | Normally we set hz(9) at compile-time in sys/conf/param.c to the value of HZ. HZ is one of the fundamental compilation options(4). However, sometimes we need to reset hz(9) at runtime. Whenever we reset hz(9) we need to recompute tick and tick_nsec. Otherwise a variety of "time stuff" in the kernel will not work correctly. For example, most timeouts will expire "too slow" or "too fast". There are a bunch of other places we use tick and tick_nsec that will exhibit similar problems. Test-compiled by deraadt@.
* use access_type as the PROT_* variable for uvm_fault() consistantlyderaadt2020-10-081-8/+8
| | | | ok kettenis
* ast() was lacking refreshcreds(). That can sleep, and mi_ast() requiresderaadt2020-09-241-4/+4
| | | | | the current cpu so use curcpu() rather than the old cpu in ci. ok kettenis
* Only perform uvm_map_inentry() checks for PROC_SP for userland pagefaults.deraadt2020-09-241-5/+7
| | | | | | | | This should be sufficient for identifying pivoted ROP. Doing so for other traps is at best opportunistic for finding a straight-running ROP chain, but the added (and rare) sleeping point has proven to be dangerous. Discussed at length with kettenis and mortimer. ok mortimer kettenis mpi
* Declare hw_{prod,serial,uuid,vendor,ver} in <sys/systm.h>.visa2020-08-261-4/+1
| | | | OK deraadt@, mpi@
* Push KERNEL_LOCK/UNLOCK() dance inside trapsignal().mpi2020-08-191-3/+1
| | | | ok kettenis@, visa@
* __main() is not need anymorederaadt2020-07-181-8/+1
|
* Use CPU_IS_PRIMARY macro on alpha and mips64.fcambus2020-07-151-2/+2
| | | | OK deraadt@, visa@
* Add support for timeconting in userland.pirofti2020-07-062-2/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | This diff exposes parts of clock_gettime(2) and gettimeofday(2) to userland via libc eliberating processes from the need for a context switch everytime they want to count the passage of time. If a timecounter clock can be exposed to userland than it needs to set its tc_user member to a non-zero value. Tested with one or multiple counters per architecture. The timing data is shared through a pointer found in the new ELF auxiliary vector AUX_openbsd_timekeep containing timehands information that is frequently updated by the kernel. Timing differences between the last kernel update and the current time are adjusted in userland by the tc_get_timecount() function inside the MD usertc.c file. This permits a much more responsive environment, quite visible in browsers, office programs and gaming (apparently one is are able to fly in Minecraft now). Tested by robert@, sthen@, naddy@, kmos@, phessler@, and many others! OK from at least kettenis@, cheloha@, naddy@, sthen@
* wire up kstat(4)dlg2020-07-061-2/+3
| | | | "looks right" deraadt@
* Remove obsolete <machine/stdarg.h> header. Nowadays the varargvisa2020-06-301-60/+0
| | | | | | | | functionality is provided by <sys/stdarg.h> using compiler builtins. Tested in a ports bulk build on amd64 by naddy@ OK naddy@ mpi@
* Implement cpu_rnd_messybits() as a read of the cycle counter register.naddy2020-06-052-12/+7
| | | | ok dlg@, powerpc/sparc64 ok kettenis@, sparc64/alpha tested by deraadt@
* introduce "cpu_rnd_messybits" for use instead of nanotime in dev/rnd.c.dlg2020-05-312-2/+13
| | | | | | | | | | | | | | | | | | | | | | | | | | 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 variousderaadt2020-05-291-2/+1
| | | | | | 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>.visa2020-05-271-58/+0
| | | | | | Nothing uses the header anymore. OK deraadt@ mpi@
* /etc/random.seed reuse can now be detected. The stat +T bit marks the filederaadt2020-05-261-1/+7
| | | | | (fchmod +T by bootcode, chmod 600 by /etc/rc). If the seed is reused, and HWRNG isn't available, the kernel won't get RB_GOODSEED indication...
* make loadrandom() return 0 for success, -1 for failure. While here,deraadt2020-05-251-11/+18
| | | | | | relax the fstat() check because the system will have left the file in the right mode. ok visa kettenis
* Pass boothowto from bootblock to kernelderaadt2020-05-253-4/+7
|
* Add support for write operations to diskstrategy().deraadt2020-05-251-3/+7
|
* remove ifdef'd out tc fb cnattach bitsjsg2020-05-231-85/+1
| | | | miod@ agrees this can go
* remove more cfb and sfb bitsjsg2020-05-234-163/+2
|
* remove cfb and sfb alpha tc fb driversjsg2020-05-236-990/+2
| | | | | | | These were removed from files.alpha 1.105 in 2017 and the rcons bits they reference were removed in 2006. removal suggested by miod@
* Put setjmp+longjmp inside #ifdef DDB the only kernel-side user.deraadt2020-05-171-1/+4
| | | | This shrinks the ramdisks a tiny bit.
* Make inittodr() and resettodr() MI.kettenis2020-05-161-93/+1
| | | | | ok deraadt@, mpi@, visa@ ok cheloha@ as well (would have preferred in new file for this code)
* Use the same inittodr()/resettodr() implementation as onkettenis2020-05-112-132/+147
| | | | | | | | amd64/arm64/armv7/hppa/i386/landisk/macppc/mips64/sparc64 and move it to the end of machdep.c. Wrap the existing clockfns hooks into something that can be used as a todr_handle. ok deraadt@
* ce examples of "Ar arg Ar arg" with "Ar arg arg" and stop the spread;jmc2020-04-231-3/+3
|
* Allow alpha boot(8) to read from an ffs2 filesystem and adapt itsotto2020-03-114-42/+147
| | | | | custom installboot to deal with ffs2. While there, fix the partition read code to deal with offsets > 2G; ok deraadt@
* The 'lock spun out' db_printf needs a newline. All other MP_LOCKDEBUGclaudio2020-03-051-2/+2
| | | | | messages do have the newline already. OK anton@ kettenis@
* Use major 32 for dt(4).mpi2020-01-241-2/+3
| | | | ok visa@, kettenis@, deraadt@
* wire up pppac(4) to some majors on each arch.dlg2020-01-231-1/+2
| | | | | | | | i was lazy and just put them at the end of the existing set. fyi, i think major 51 is free on all archs if anyone is looking for another one. ok claudio@
* Add fido(4), a HID driver for FIDO/U2F security keysreyk2019-12-172-2/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | While FIDO/U2F keys were already supported by the generic uhid(4) driver, this driver adds the first step to tighten the security of FIDO/U2F access. Specifically, users don't need read/write access to all USB/HID devices anymore and the driver also improves integration with pledge(2) and unveil(2): It is pledge-friendly because it doesn't require any ioctls to discover the device and unveil-friendly because it uses a single /dev/fido/* directory for its device nodes. It also allows to support FIDO/U2F in firefox without further weakening the "sandbox" of the browser. Firefox does not have a proper privsep design and many operations, such as U2F access, are handled directly by the main process. This means that the browser's "fat" main process needs direct read/write access to all USB HID devices, at least on other operating systems. With fido(4) we can support security keys in Firefox under OpenBSD without such a compromise. With this change, libfido2 stops using the ioctl to query the device vendor/product and just assumes "OpenBSD" "fido(4)" instead. The ioctl is still supported but there was no benefit in obtaining the vendor product or name; it also allows to use libfido2 under pledge. With feedback from deraadt@ and many others OK kettenis@ djm@ and jmc@ for the manpage bits
* Remove unused test program.visa2019-12-011-62/+0
| | | | OK deraadt@
* The compiler -pg option implies -fno-ret-protector, as we want to disableguenther2019-11-071-2/+2
| | | | | | | | | | | retguard and similar when profiling. However, that missed all the .S files, as ${PROF} wasn't added when ${NORMAL_S} was converted from direct invocation of ${AS} to instead use ${CC}. Similarly, mcount.o still had retguards as it cannot be built with -pg. So: pass ${PROF} when compiling .S files, and compile "no profiling" files with -fno-ret-protector on archs with retguard. feedback and ok mpi@ mortimer@
* Convert db_addr_t -> vaddr_t but leave the typedef for now.mpi2019-11-074-23/+23
|
* ANSIfy & substitute boolean_t/TRUE/FALSE by int/1/0.mpi2019-11-073-65/+40
| | | | ok jasper@, deraadt@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.