OpenBSD cvs log

created 2020-09-06T08:01:20Z
begin 2020-09-03T00:00:00Z
end 2020-09-04T00:00:00Z
path src/sys
commits 5

date 2020-09-03T12:41:28Z
author krw
files src/sys/arch/sparc64/dev/vdsk.c log diff annotate
src/sys/dev/softraid.c log diff annotate
message Replace '.response_format = 2' with '.response_format = SID_SCSI2_RESPONSE'.

date 2020-09-03T12:41:29Z
author krw
files src/sys/dev/ata/atascsi.c log diff annotate
src/sys/dev/ic/aac.c log diff annotate
src/sys/dev/ic/ami.c log diff annotate
src/sys/dev/ic/cac.c log diff annotate
src/sys/dev/ic/gdt_common.c log diff annotate
src/sys/dev/ic/nvme.c log diff annotate
src/sys/dev/ic/twe.c log diff annotate
src/sys/dev/pci/ips.c log diff annotate
src/sys/dev/pv/hvs.c log diff annotate
src/sys/dev/pv/vioblk.c log diff annotate
src/sys/dev/pv/xbf.c log diff annotate
src/sys/dev/sdmmc/sdmmc_scsi.c log diff annotate
message Replace '.response_format = 2' with '.response_format = SID_SCSI2_RESPONSE'.

date 2020-09-03T15:30:17Z
author kettenis
files src/sys/dev/wscons/wsdisplay_compat_usl.c log diff annotate
message The "USL" VT switch and keyboard ioctls are a hack and don't follow the
proper BSD way where the third argument is always a pointer and data is
transferred between userland and kernel using copyin(9) and copyout(9).
Intead an int is encoded in the thirs argument. This works on 32-bit
architectures and little-endian 64-bit architectures. But not on
big-endian 64-bit architectures. Deal with this by handling the argument
as long (which matches the size of a pointer).

Hopefully we can eliminate these ioctls in the near future.

ok deraadt@

date 2020-09-03T20:02:02Z
author kettenis
files src/sys/arch/powerpc64/dev/xive.c log diff annotate
message Sprinkle some more eieio(); seems to avoid triggering the KASSERT(new > old).

date 2020-09-03T21:38:46Z
author cheloha
files src/sys/arch/amd64/amd64/lapic.c log diff annotate
message amd64: lapic: refactor timer programming

We reprogram the lapic timer by hand in three separate places.
This is error-prone and difficult to read.

To clean things up, introduce routines for reprogramming the lapic
timer in a given mode. lapic_timer_oneshot() starts a oneshot
countdown. lapic_timer_periodic() starts a repeating countdown.

Both of these routines call lapic_timer_start(), wherein we actually
write the lapic registers.

With input from dlg@.

Earlier version eyeballed by mlarkin@.

Suspend/resume tested by gnezdo@.