OpenBSD cvs log

created 2024-03-04T12:44:42Z
begin 2024-02-24T00:00:00Z
end 2024-02-25T00:00:00Z
path src/sys
commits 3

date 2024-02-24T01:43:32Z
author cheloha
files src/sys/kern/kern_clockintr.c log diff annotate
message clockintr: rename clockqueue_reset_intrclock to clockqueue_intrclock_reprogram

The function should be in the clockqueue_intrclock namespace. Also,
"reprogram" is a better word for what the function actually does.

date 2024-02-24T15:21:39Z
author cheloha
files src/sys/dev/ic/qwx.c log diff annotate
src/sys/dev/ic/qwxvar.h log diff annotate
message qwx(4): qwx_dp_rx_tid_del_func: fix dp_reo_cache_flush_elem expiration logic

Tweak a few things in qwx_dp_rx_tid_del_func() to make it behave
correctly on OpenBSD:

- struct dp_reo_cache_flush_elem: make ts a 64-bit count of nanoseconds

Linux uses jiffies to timestamp dp_reo_cache_flush_elem. Although
OpenBSD has a global jiffies variable, we shouldn't use it outside
of drm(4). I would rather not use our global ticks variable, either.
We can use getnsecuptime(9), a low-res 64-bit nanosecond timestamp,
as a substitute.

- qwx_dp_rx_tid_del_func: replace gettime(9) with getnsecuptime(9)

- qwx_dp_rx_tid_del_func: convert DP_REO_DESC_FREE_TIMEOUT_MS to nanoseconds

- qwx_dp_rx_tid_del_func: reverse timestamp comparison operator

This comparison is backwards. Linux uses the time_after() macro to
test whether a given entry has expired, so our ported code needs to
test whether the current uptime is greater than or equal to a given
entry's expiration time.

Joint effort with stsp@. Tested by stsp@.

ok stsp@

date 2024-02-24T17:00:05Z
author deraadt
files src/sys/arch/amd64/amd64/cpu.c log diff annotate
message Explicitly disable MSR_CET_NO_TRACK_EN in MSR_S_CET. If enabled by the
boot-process, we don't want to accidentally allow "notrack" indirect
branches. Linux kernel does the same. Today it is difficult to do the
same for userland, because there is 1 known piece of software using
"notrack" (which needs to be fixed).
ok kettenis