OpenBSD cvs log

created 2022-07-16T16:50:50Z
begin 2022-07-12T00:00:00Z
end 2022-07-13T00:00:00Z
path src/sys
commits 10

date 2022-07-12T03:55:34Z
author jsg
files src/sys/arch/arm64/arm64/cpu.c log diff annotate
message recognise Cortex-A715 and Cortex-X3

date 2022-07-12T04:46:00Z
author jsg
files src/sys/arch/amd64/amd64/cacheinfo.c log diff annotate
src/sys/arch/amd64/amd64/identcpu.c log diff annotate
src/sys/arch/amd64/amd64/vmm.c log diff annotate
src/sys/arch/amd64/include/cpu.h log diff annotate
message remove cache parts of struct cpu_info only vmm used
suggested by and ok mlarkin@

date 2022-07-12T04:52:38Z
author jsg
files src/sys/arch/amd64/amd64/vmm.c log diff annotate
message allow cpuid 0x8000001d, cache topology on AMD
ok mlarkin@

date 2022-07-12T05:45:49Z
author jsg
files src/sys/arch/i386/i386/machdep.c log diff annotate
src/sys/arch/i386/include/cpu.h log diff annotate
message remove cache parts of struct cpu_info which were used by vmm

date 2022-07-12T08:58:53Z
author mvs
files src/sys/net/pipex.c log diff annotate
src/sys/net/pipex.h log diff annotate
src/sys/net/pipex_local.h log diff annotate
message Remove PIPEXCSESSION pipex(4) ioctl(2) command from kernel and man page.

Long time ago pipex(4) session can't be deleted until both pipex(4)
input and output queues become empty. Dead sessions were linked to the
stack and the `ip_forward' flag was used to prevent packets forwarding.
npppd(8) marked such sessions by doing PIPEXCSESSION ioctl(2) call.

But since we started to unlink close session from the stack, this logic
became unnecessary. Also pipex(4) session could be closed just after
close request.

npppd(8) was the only userland program which did PIPEXCSESSION ioctl(2)
call, and we removed it week ago. It's time to remove the remains.

Now the `flags' member of 'pipex_session' structure became immutable.

ok yasuoka@

date 2022-07-12T17:12:31Z
author jca
files src/sys/conf/files log diff annotate
src/sys/ddb/db_rint.c log diff annotate
src/sys/sys/systm.h log diff annotate
message Add db_rint(), an MI interface to db_enter() copied from kdbrint() in vax code

If ddb.console is set and your serial console driver uses it, db_rint(),
lets you enter ddb(4) by typing the ESC D escape sequence. This is
useful for drivers like sfuart(4) where the hardware doesn't have a true
BREAK mechanism.

Suggested by miod@, ok kettenis@ miod@

date 2022-07-12T17:14:12Z
author jca
files src/sys/arch/riscv64/dev/sfuart.c log diff annotate
message Use db_rint() in sfuart(4)

This lets me enter ddb(4) even when the riscv64 machines I manage get
unusable because of NFS.

Suggested by miod@, ok miod@ kettenis@

date 2022-07-12T22:08:17Z
author bluhm
files src/sys/dev/ic/gem.c log diff annotate
message Protect interface media list with a mutex. This is just a start
to make make media structures MP safe.
OK mvs@

date 2022-07-12T22:08:18Z
author bluhm
files src/sys/net/if_media.c log diff annotate
src/sys/net/if_media.h log diff annotate
message Protect interface media list with a mutex. This is just a start
to make make media structures MP safe.
OK mvs@

date 2022-07-12T22:27:38Z
author bluhm
files src/sys/net/if_media.c log diff annotate
message Use __func__ in interface media debug printf().