Age | Commit message (Collapse) | Author |
|
become interesting in the future.
ok deraadt krw
|
|
space-saving candidate is found
(this candidate selected by jsg and kettenis, don't blame the commiter)
|
|
ok deraadt krw
|
|
require the debugger on most architectures, and the separation makes the
code easier to use from other subsystems.
The function definitions are still conditional to DDB. However, that
should not matter for now.
OK deraadt@, mpi@
|
|
Tested by kn@, ok kettenis@, kn@
|
|
For now, this driver fetches the "chip id" and feeds this as entropy
to the kernel's random subsystem.
|
|
|
|
in ticks was meant to be in msecs.
Pointed out by and ok patrick@
|
|
seconds and use tsleep_nsec(9).
ok patrick@
|
|
ok patrick@
|
|
efiboot was loaded from. Code taken from arm64 with softraid support
dropped for now.
ok jsg@
|
|
|
|
from alex naumov
|
|
ok cheloha@
|
|
There are no units noted here, but macppc is a 100hz platform so it's safe
to just assume 2500 milliseconds here.
ok jsg@
|
|
and pass information to ddb. This helps to debug kernel NULL pointer
function calls.
input guenther@; OK kettenis@
|
|
BP cache if necessary).
ok patrick@
|
|
arm64 version and fixes some (but not all) remaining issues with SMP support
on armv7.
ok visa@, patrick@
|
|
|
|
ok mpi@
|
|
No object change; I forgot to commit this together with
sys/dev/pci/mpii.c
revision 1.125
date: 2020/01/03 08:39:31; author: kn; state: Exp; lines: +10 -1;
Fix RAID volume WWIDs for LSI controllers on sparc64
Some controllers generate 128 bit WWIDs for RAID volumes but only has a
bit field to report it to the host, so it only puts the
vendor-specified part here (last half of ID string printed when sd*
attaches matches sl->port_wwn in reverse).
As such IDs are not IEEE NAA compliant, OpenBoot PROM -at least on SPARC-
sets the highest nibble to three by convention to mark such volumes as
RAID volumes so that the OS (Solaris) may identify it as such.
This is the last missing piece to make booting off hardware RAID on sparc64
just work; autoconf(9) is now able to match the port WWN against the
bootpath to eventually identify the volume as the root device.
Feedback jmatthew deraadt
OK jmatthew
|
|
From miod@
|
|
time processing. That was sometimes observed when the system get
heavy load, like 'make -j N build'.
|
|
ok mortimer@ mpi@ deraadt@
|
|
OK miod@
|
|
|
|
introduced iommu_dvmamap_insert() using an undefined paddr_t pa under DEBUG;
since it cannot be introduced it (easily), remove it from the printf().
|
|
|
|
Feedback guenther
|
|
make the structs const so that the data are put in .rodata.
OK mpi@, deraadt@, anton@, bluhm@
|
|
Tested by and ok aoyama@
|
|
Allied Telesis CentreCOM LA-98 works well, other NE2000 based boards
may also work with correct resource specifying.
This driver was developed for demonstration at Open Source Conference
2019 Nagoya, Japan, in July, but I forgot to commit after that:-)
|
|
Fixes booting on ACPI machines where the MADT table lists CPUs that
are disabled such as the od1000 with new EDK2 firmware.
|
|
|
|
during kernel startup before syslogd(8) can receive it. Increase
message buffer size from 94k to 128k on amd64.
reported by Hrvoje Popovski; OK deraadt@
|
|
Document the new feature in boot(8) man page.
OK jmc@ deraadt@
|
|
AMD SoCs/chipsets.
From James Hastings
|
|
ok deraadt@
|
|
OK mpi@
|
|
OK mpi@
|
|
Rename variables for clarity while here.
OK mpi@
|
|
|
|
Even with the latest microcode this is not set on all CPUs with TSX, but
is set on CPUs which don't need MDS mitigations.
MDS mitigations also mitigate TSX Asynchronous Abort (TAA) but aren't
done if the CPU claims to not be affected by MDS (MDS_NO).
According to "Deep Dive: Intel Transactional Synchronization Extensions
(Intel TSX) Asynchronous Abort" CPUs requiring additional mitigations
for this are:
06-8e-0c Whiskey Lake (ULT refresh)
06-55-0{6,7} 2nd Gen Xeon Scalable Processors based on Cascade Lake
06-9e-0d Coffee Lake R
Currently TSX is disabled unconditionally when possible even if TAA_NO
is set.
We don't currently do MDS mitigations on i386. Attempt to disable TSX
regardless to match amd64.
|
|
Even with the latest microcode this is not set on all CPUs with TSX, but
is set on CPUs which don't need MDS mitigations.
MDS mitigations also mitigate TSX Asynchronous Abort (TAA) but aren't
done if the CPU claims to not be affected by MDS (MDS_NO).
According to "Deep Dive: Intel Transactional Synchronization Extensions
(Intel TSX) Asynchronous Abort" CPUs requiring additional mitigations
for this are:
06-8e-0c Whiskey Lake (ULT refresh)
06-55-0{6,7} 2nd Gen Xeon Scalable Processors based on Cascade Lake
06-9e-0d Coffee Lake R
Currently TSX is disabled unconditionally when possible even if TAA_NO
is set.
ok bluhm@ guenther@ deraadt@
tested by bluhm@ on i5-8365U (06-8e-0c).
|
|
the kernel.
ok patrick@
|
|
the kernel.
ok mlarkin@, visa@
|
|
the kernel.
ok mlarkin@, visa@
|
|
Some drivers have returned ENXIO (6) if the device is not available
which incorrectly translates into POLLPRI|POLLOUT (2|4) in userland.
Change it to POLLERR for now, but it might as well be POLLHUP.
OK mpi@
|
|
|
|
processors not all microarchitectural side effects are abandoned,
leading to spectre-like effects. This was fixed quietly and without
responsible disclosure by ARM in linux mainline a year ago, but
rediscovered independently by Anthony Steinhauser. ok patrick
guenther kettenis
comment to ARM: "Responsible Disclosure" doesn't mean "downplay at
maximum to avoid damage to the bottom line", the responsibility aspect
entails ensuring "all customers are aware of the defect". What
happened here is indistinguishable from Intel's behaviour, and that's
not the look you want.
|