OpenBSD cvs log

created 2022-06-04T18:43:40Z
begin 2022-06-01T00:00:00Z
end 2022-06-02T00:00:00Z
path src/sys
commits 12

date 2022-06-01T03:34:21Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
src/sys/dev/fdt/if_mvnetareg.h log diff annotate
message rework tx start and completion.

this is a big step toward making the code mpsafe, and makes a bunch
of ring operations such as dmamap syncs and register updates per
start/completion call rather than per packet.

date 2022-06-01T03:37:41Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
message trim some white space

date 2022-06-01T03:39:57Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
message dont have to say Ethernet address in dmesg, address is fine

date 2022-06-01T03:51:19Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
message mark mvneta_start mpsafe.

the interrupt handler is still under kernel lock, but at least you
can queue packets from another cpu concurrently.

date 2022-06-01T04:31:08Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
src/sys/dev/fdt/if_mvnetareg.h log diff annotate
message rework the rx ring processing.

this is another big step toward making the code mpsafe, and makes
a bunch of ring operations such as dmamap syncs and register updates
get done once for the ring rather than for every packet.

date 2022-06-01T06:33:46Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
message mark the mvneta interrupt handler as mpsafe.

link state changes still take the kernel lock, but packet processing
is unlocked now.

date 2022-06-01T08:19:15Z
author dlg
files src/sys/dev/fdt/if_mvneta.c log diff annotate
message shrink dmesg output by printing the ethernet address on the attach line.

date 2022-06-01T14:16:28Z
author visa
files src/sys/kern/vfs_lockf.c log diff annotate
message Fix lock range start when l_whence == SEEK_END and l_len < 0.

OK anton@

date 2022-06-01T14:18:43Z
author visa
files src/sys/kern/vfs_lockf.c log diff annotate
message Fix ambiguity with lock range end

When the user requests a lock range that ends at LLONG_MAX, replace
the end point with the special EOF value -1. This avoids ambiguity
with lf_end in lf_split(). The ambiguity could result in a broken
data structure.

This change is visible to userspace in a corner case. When a lock range
has been requested with an end point at absolute position LLONG_MAX,
fcntl(F_GETLK) returns l_len == 0, instead of a positive value, for that
range. This seems consistent with FreeBSD and Linux.

OK anton@

Reported-by: [email protected]

date 2022-06-01T17:16:00Z
author dv
files src/sys/arch/i386/include/pmap.h log diff annotate
message remove unused pmap_convert prototype from i386

Leftover lint from early days of vmm(4).

ok mlarkin@

date 2022-06-01T17:34:13Z
author sashan
files src/sys/net/if_veb.c log diff annotate
message callers to pf(4) must continue to run with packet as returned
by firewall.

OK dlg@

date 2022-06-01T17:47:18Z
author dv
files src/sys/arch/amd64/amd64/pmap.c log diff annotate
src/sys/arch/amd64/amd64/vmm.c log diff annotate
src/sys/arch/amd64/include/pmap.h log diff annotate
message change amd64 pmap_convert to return void

There are no other return options, so adjust function signature to
void. This also allows for cleaning up its usage in vmm(4) in the
vm pmap initialization logic.

ok mlarkin@