OpenBSD cvs log

created 2019-06-01T11:00:52Z
begin 2019-05-28T00:00:00Z
end 2019-05-29T00:00:00Z
path src/sys
commits 7

date 2019-05-28T04:51:26Z
author mlarkin
files src/sys/arch/amd64/include/loadfile_machdep.h log diff annotate
message Remove a 15 year old XXX comment

date 2019-05-28T08:44:27Z
author sf
files src/sys/arch/i386/conf/GENERIC log diff annotate
message Enable virtio again since the compilation problems have been fixed.

ok deraadt@

date 2019-05-28T17:38:02Z
author mlarkin
files src/sys/arch/amd64/stand/libsa/exec_i386.c log diff annotate
message Cleanup some bootloader code

Refactoring to remove 'long_kernel' variable and consistent use of 'entry'
and 'marks[MARK_ENTRY]'. Prompted by guenther@. No functional change.

tested by jca@ and myself

ok guenther@, kettenis@

date 2019-05-28T18:17:01Z
author guenther
files src/sys/arch/amd64/amd64/cpu.c log diff annotate
message Skip doing MDS mitigation on vmm entry if the new firmware is present,
as it enhances the L1D_FLUSH MSR to flush MDS too

ok mlarkin@

date 2019-05-28T18:20:01Z
author guenther
files src/sys/arch/amd64/amd64/identcpu.c log diff annotate
message Correct the test for when the L1TF vulnerablity has been mitigated via
either hardware update (RDCL_NO) or our being nested in a VM which is
handling the flushing via the L1D_FLUSH MSR.

ok mlarkin@

date 2019-05-28T18:39:06Z
author kn
files src/sys/net/bfd.c log diff annotate
message Fix reporting of up->down transition in routing message

The code for updating the laststate and timer is looking at laststate before
it's been updated.

From Mitchell Krome , thanks!

OK claudio

date 2019-05-28T20:32:30Z
author patrick
files src/sys/arch/arm64/arm64/locore.S log diff annotate
src/sys/arch/arm64/arm64/locore0.S log diff annotate
src/sys/arch/arm64/arm64/machdep.c log diff annotate
src/sys/arch/arm64/arm64/pmap.c log diff annotate
message On bigger arm64 machines with plenty of memory it is possible that
the kernel, which is allocated in low memory by efiboot, is not in
the same 512 GiB L0 address space as the EFI/FDT/ACPI tables. Since
we only identity-map a single L0 entry for bootstrapping purposes we
can't reach those tables. Keep a set of spare L1 tables, currently
one, which we can dynamically enter into the identity map so that we
are able to reach those tables. While there, do the FDT mapping a
bit later in C code by calling pmap_map_early(). This allows us to
boot further on Packet's Ampere eMAGs.

Discussed with drahn@
ok kettenis@