OpenBSD cvs log

created 2021-09-05T05:02:55Z
begin 2021-09-03T00:00:00Z
end 2021-09-04T00:00:00Z
path src/sys
commits 11

date 2021-09-03T11:41:41Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
src/sys/dev/pci/if_iwx.c log diff annotate
message Ensure that iwm(4) and iwx(4) will reload firmware from disk on down/up,
and will not do so during resume.

Tested by kevlo@ on iwx(4) and by myself on iwm(4).

date 2021-09-03T11:47:05Z
author dv
files src/sys/arch/amd64/amd64/vmm.c log diff annotate
message vmm(4): grab kernel lock before vmspace init

We need the kernel lock before calling some uvm functions. Fixes a
panic reported by syzbot.

Reported-by: [email protected]

ok mlarkin@

date 2021-09-03T11:55:31Z
author stsp
files src/sys/dev/pci/if_iwm.c log diff annotate
src/sys/dev/pci/if_iwx.c log diff annotate
message Make iwm(4) and iwx(4) resume code path more similar to the attach code path.

In particular, this makes suspend/resume work on systems using msix.
Resume is not 100% reliable yet, though, failing about 1 in 20 times
to bring the interface back up.
Recovery with ifconfig down/up should be possible when things go wrong.

With help from gnezdo@ in diagnosing the issue and testing changes.

Tests:
8265: stsp
9260: florian
9560: kevlo, Uwe Werler
ax200: kevlo, Mark Patruck, beck
ax201: gnezdo

date 2021-09-03T12:39:43Z
author stsp
files src/sys/net80211/ieee80211_input.c log diff annotate
message Reset a net80211 node's QoS Tx sequence counter to the start of the
block ack window when a new Tx block ack agreement is established.

In the future this change will allow the iwx(4) driver to initialize this
sequence number such that it corresponds to what the firmware expects.

Note that ba->ba_winstart is set to ni->ni_qos_txseqs[tid] when a new Tx agg
agreement is initiated in ieee80211_node_addba_request(). Unless the driver
resets ba->ba_winstart before ieee80211_addba_resp_accept() runs, which is
what iwx(4) will do, the assignment added with this patch is a no-op.

date 2021-09-03T14:04:35Z
author patrick
files src/sys/dev/pci/virtio_pci.c log diff annotate
message Make virtio(4) less restrictive on the type of BAR it supports for
legacy versions. The current version of Parallels on M1 seems to
not provide the I/O BAR that we expect, and reducing our expectations
seems to be help.

ok kettenis@

date 2021-09-03T14:09:26Z
author jca
files src/sys/arch/riscv64/include/ptrace.h log diff annotate
message Enable ptrace(2) support for PT_GETFPREGS/PT_SETFPREGS

The code is already there, it was unreachable because of this #if 0.
ok kettenis@

date 2021-09-03T14:13:06Z
author jca
files src/sys/arch/riscv64/include/ptrace.h log diff annotate
message Don't pretend we support PT_STEP on this architecture.

The RISC-V doesn't seem to provide hardware support for generic purpose
single stepping, and we're not emulating single stepping for riscv64
like we do for alpha or mips64. Hiding PT_STEP makes it possible to run
inferior processes with a wip ports/devel/gdb update.

ok kettenis@

date 2021-09-03T14:53:09Z
author patrick
files src/sys/arch/arm64/conf/GENERIC log diff annotate
src/sys/arch/arm64/conf/RAMDISK log diff annotate
message It's time to enable smmu(4).

ok kettenis@ some time ago

date 2021-09-03T14:58:25Z
author jca
files src/sys/arch/riscv64/riscv64/trap.c log diff annotate
message Zap a chatty printf

ok mlarkin@ kettenis@

date 2021-09-03T16:45:44Z
author jasper
files src/sys/arch/amd64/amd64/vector.S log diff annotate
src/sys/arch/i386/i386/locore.s log diff annotate
message add kprobes provider for dt

this allows us to dynamically trace function boundaries with btrace by patching
prologues and epilogues with a breakpoint upon which the handler records the data,
sends it back to userland for btrace to consume.
currently it's hidden behind DDBPROF, and there is still a lot to cleanup and
improve, but basic scripts that observe return codes from a probed function
work.

from Tom Rollet, with various changes by me
feedback and ok mpi@

date 2021-09-03T16:45:45Z
author jasper
files src/sys/conf/files log diff annotate
src/sys/ddb/db_prof.c log diff annotate
src/sys/dev/dt/dt_dev.c log diff annotate
src/sys/dev/dt/dt_prov_kprobe.c log diff annotate
src/sys/dev/dt/dt_prov_profile.c log diff annotate
src/sys/dev/dt/dt_prov_static.c log diff annotate
src/sys/dev/dt/dt_prov_syscall.c log diff annotate
src/sys/dev/dt/dtvar.h log diff annotate
src/sys/kern/subr_prof.c log diff annotate
message add kprobes provider for dt

this allows us to dynamically trace function boundaries with btrace by patching
prologues and epilogues with a breakpoint upon which the handler records the data,
sends it back to userland for btrace to consume.
currently it's hidden behind DDBPROF, and there is still a lot to cleanup and
improve, but basic scripts that observe return codes from a probed function
work.

from Tom Rollet, with various changes by me
feedback and ok mpi@