Age | Commit message (Collapse) | Author |
|
(stirng -> string)
ok kettenis@ who pointed out I should fix the new arm64 smbiosvar.h too
|
|
or sending an IPI.
|
|
|
|
differences between the i386 and amd64 versions of the code and
switch to using the standard C integer exact width integer types.
ok deraadt@
|
|
|
|
|
|
ok deraadt@, jsg@
|
|
|
|
approach was not right, and there is still room for improvement.
OK deraadt@
|
|
|
|
|
|
ok kettenis
|
|
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade.
Now various forms of upgrade failure will reboot into /bsd, which is probably
more recoverable. Performing fchmod -x depends on (1) use of MI boot.c
(not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality
in the IO layer. Most architectures have this support now.
Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will
remain in the tree while refinements happen for some of the laggard
architectures.
based upon a discussion florian
tested in snapshots for more than a week without any complaints
|
|
for lapic timer init to avoid calibrating against the 8254 clock.
Some newer machines are shipping with the 8254 clock gated for power
saving, so it may not be usable.
ok mlarkin
discussed with deraadt
|
|
processor identification purposes. Use the name instead of the ID as
the sentinel in the various tables since X-Gene has PartNum zero.
Note that this means Ampere eMAG gets recognized as Applied Micro
X-Gene r3p2. That makes sense as the CPU started its life as X-Gene 3.
Apparently future Ampere parts will use the new Ampere Implementer ID.
ok jsg@
|
|
enough memory for the device table to cover the entire DeviceID space.
ok patrick@
|
|
|
|
get updated when handling an AST after an interrupt.
OK deraadt@
|
|
Loongson runs at 128hz. 128 doesn't divide evenly into a million,
but it does divide evenly into a billion. So if we do the per-process
itimer bookkeeping with itimerspec structs we can have error-free
virtual itimers on loongson just as we do on most other platforms.
This change doesn't fix the virtual itimer error alpha, as 1024 does not
divide evenly into a billion. But this doesn't make the situation any
worse, either.
ok deraadt@
|
|
|
|
were free after the kernel was loaded. The memory occupied by the kernel
image is not included. To let libkvm access the image through /dev/kmem,
return true from is_memory_range() if the physical address is within
the kernel.
|
|
|
|
of the ICC_PMR_EL1 registers varies with the value being written. Change the
value we write to probe the number of writable bits to a value that yields
the desired result.
Suggested by drahn@
ok patrick@
|
|
fit into the 39-bit address space that we currently use for the runtime
mappings.
ok patrick@
|
|
noticed by tb@
|
|
ok patrick deraadt
|
|
|
|
KNF, no code change.
|
|
OK deraadt@
|
|
the size of the "boot" file.
OK deraadt@
|
|
in the bootloader.
|
|
kernel handover safer.
|
|
|
|
such busses.
|
|
"yes please" guenther@
|
|
|
|
|
|
|
|
jan@ has a machine where the smbios date is ten space characters which
results in fixstring() returning NULL causing a NULL derefence.
Reported, tested by and ok jan@
|
|
because UEFI on 32-bit ARM is supposed to leave them enabled and U-boot
was changed (starting with release 2019.04) to follow the spec here. However
the OpenBSD/armv7 kernel expects to be booted with caches and MMU turned off.
Note that there are still issues on boards that enable the non-architected
L2 cache. UEFI demands that such caches are not turned on, but U-Boot
does turn them on and this makes our kernel fail to boot.
With help from jsg@
ok jsg@
|
|
From Christian Ludwig <christian_ludwig at genua dot de>
ok visa@
|
|
ok visa@
|
|
Back in the mid-90s these optimizations probably made sense, but
these days the compiler will produce even better code if we just
explicitly use 64-bit math and do the obvious thing.
joerg@netbsd.org even popped in on tech@ to agree.
ok guenther@
|
|
All callers sleep indefinitely.
With help from visa@.
ok visa@, ratchov@, kn@
|
|
|
|
|
|
The firmware on OCTEON machines usually does not provide an interface
for accessing devices, which has made it tricky to implement an OpenBSD
bootloader. To solve this device access problem, this new loader has
been built on top of a small kernel. The kernel provides all the
necessary devices drivers, while most of the usual bootloader logic
is in a userspace program in a ramdisk.
The loader program is accompanied by a special device, octboot(4).
The main purpose of this device is to implement a mechanism for
loading and launching kernels. The mechanism has been inspired by Linux'
kexec(2) system call.
The bootloader will be enabled later when it is ready for general use.
Discussed with deraadt@
|
|
Implement VMM_IOC_READVMPARAMS and VMM_IOC_WRITEVMPARAMS ioctls to read and
write pvclock state.
reads ok mlarkin@
|
|
memory (or, more precisely, those machines that had physical memory
regions extending past physical address 1023GB).
ok kettenis
|
|
ok mlarkin@ kettenis@
|