OpenBSD cvs log

created 2023-03-26T22:09:09Z
begin 2023-03-19T00:00:00Z
end 2023-03-20T00:00:00Z
path src/sys
commits 10

date 2023-03-19T06:02:07Z
author jsg
files src/sys/conf/GENERIC log diff annotate
message disable POOL_DEBUG for release
ok deraadt@

date 2023-03-19T08:41:49Z
author kettenis
files src/sys/dev/fdt/if_dwqe_fdt.c log diff annotate
message Use a task to switch clocks on RK3568 as the clock API needs process context.

ok jmatthew@

date 2023-03-19T09:32:11Z
author kettenis
files src/sys/dev/fdt/rkclock.c log diff annotate
src/sys/dev/fdt/rkclock_clocks.h log diff annotate
message Add a few more RK3568 clocks.

ok dlg@

date 2023-03-19T09:38:06Z
author jsg
files src/sys/dev/pci/pcidevs log diff annotate
src/sys/dev/pci/drm/amd/amdgpu/amdgpu_devlist.h log diff annotate
message add another Navi 33 device id

0x7483 rev 0xcf is Radeon RX 7600M according to
Radeon Software for Linux version 22.40.3 (5.4.3) libdrm-amdgpu-common

date 2023-03-19T09:38:43Z
author jsg
files src/sys/dev/pci/pcidevs.h log diff annotate
src/sys/dev/pci/pcidevs_data.h log diff annotate
message regen

date 2023-03-19T09:46:40Z
author kettenis
files src/sys/dev/ic/dwqevar.h log diff annotate
message Use a task to switch clocks on RK3568 as the clock API needs process context.

ok jmatthew@

date 2023-03-19T10:18:17Z
author dlg
files src/sys/dev/fdt/rkclock.c log diff annotate
message improve dmesg output to help with debugging.

for SoCs that can provide multiple instances of rkclock, let them
provide a name that will be printed during attach so you can tell
which one is doing what.

when rkclock_set_frequency isn't handling a clock, have it print
which rkclock instance isn't handling a clock. while here, print
the clock index the same way the #define refers to them.

ok kettenis@

date 2023-03-19T11:17:16Z
author kettenis
files src/sys/dev/fdt/files.fdt log diff annotate
src/sys/dev/fdt/rkpciephy.c log diff annotate
message Add rkpciephy(4), ad friver for the PCIe 3.0 PHY dound on the RK356x.
The driver in principle supports bifurcation but this is (largely) untested.

ok dlg@

date 2023-03-19T11:18:11Z
author kettenis
files src/sys/arch/arm64/conf/GENERIC log diff annotate
src/sys/arch/arm64/conf/RAMDISK log diff annotate
message Enable rkpciephy(40.

date 2023-03-19T20:32:13Z
author kettenis
files src/sys/arch/amd64/include/vmparam.h log diff annotate
src/sys/arch/arm64/include/vmparam.h log diff annotate
src/sys/arch/mips64/include/vmparam.h log diff annotate
src/sys/arch/powerpc64/include/vmparam.h log diff annotate
src/sys/arch/riscv64/include/vmparam.h log diff annotate
src/sys/arch/sparc64/include/vmparam.h log diff annotate
src/sys/kern/exec_subr.c log diff annotate
message Aggressively randomize the location of the stack on all 64-bit architectures
except alpha. This will put the stack at a random location in the upper
1/4th of the userland virtual address space providing up to 26 additional
bits of randomness in the address. Skip alpha for now since it currently
puts the stack at a (for a 64-bit architecture) very low address. Skip
32-bit architectures for now as well since those have a much smaller
virtual address space and we need more time to figure out what a safe
amount of extra randomizations is. These architectures will continue to
use a mildly randomized stack address through the existing stackgap random
mechanism. We will revisit this after 7.3 is released.

This should make it harder for an attacker to find the stack.

ok deraadt@, miod@