src/sys, branch main

vnlru: avoid trigger calculation when force < 2

2026-05-19T18:07:57Z

Reviewed by: kib (previous version), olce Sponsored by: Dell Inc. Differential Revision: https://reviews.freebsd.org/D56950

arm64/iommu: Add a missing close parenthesis

2026-05-19T17:30:01Z

Fixes: 6dc813301a17 ("sys: Use is_pci_device instead of direct comparisons to devclasses") Sponsored by: Chelsio Communications

vnic: Add missing #include

2026-05-19T17:18:00Z

Reported by: bz, olivier Fixes: 6dc813301a17 ("sys: Use is_pci_device instead of direct comparisons to devclasses") Sponsored by: Chelsio Communications

linuxkpi: fix 32-bit arm build

2026-05-19T13:47:35Z

The new KPI is only used in , but it's provided in linux_page.c. The latter only includes the former indirectly by way of , and that's only conditionally included outside of 32-bit ARM there. All of our archs have the necessary pmap_page_set_memattr(), so just move the declaration into instead of trying to reason about the usability of directly in linux_page.c. Reported by: jenkins (via ivy)

snd_hda: Reassign duplicate HDMI/DP pin sequences instead of disabling

2026-05-19T12:25:51Z

Some firmware (e.g. Apple EFI on Sandy Bridge Mac hardware) programs all HDMI/DP output pins in an association with identical sequence numbers. The existing code disables the entire association on the first duplicate, leaving HDMI/DP audio non-functional. For digital output pins (HDMI/DP) with seq=0 duplicates, search for the next free sequence slot and reassign the duplicate rather than disabling. The seq=0 restriction targets the known Apple firmware pattern; any other duplicate sequence is more likely a genuine firmware error and the association is still disabled. Update first after reassignment so that hpredir is not left pointing at a stale sequence. Non-digital and input associations retain the existing disable behaviour. MFC after: 1 week Reviewed by: christos Differential Revision: https://reviews.freebsd.org/D55473

tmpfs: Overhaul option handling on remount

2026-05-19T06:54:28Z

On remount, we must accept all the same options as on initial mount. For parameters which we're unable to modify on the fly, fail only if the new value is different from the existing one. PR: 295096 MFC after: 1 week Reviewed by: kib Differential Revision: https://reviews.freebsd.org/D57044

net80211: migrate wk_rxmic / wk_rxmic in TKIP code to accessors

2026-05-19T05:28:49Z

These are the last two uses of the wk_rxmic / wk_txmic macros. Everything should be using the accessor methods at ths point. Reviewed by: bz Differential Revision: https://reviews.freebsd.org/D54790

iwx: clean up / document noise floor and RSSI fetching

2026-05-19T05:27:59Z

* Document what iwx_rxmq_get_signal_strength() is doing in a comment, noting what the firmware returns and what math is being done on it to turn it into a dBm value. * Document what iwx_get_noise() is supposed to do, that we can't just go do math with log numbers like we're doing, but also that we're seeing zeros in this firmware (AX210), which may mean we're decoding using the wrong structs. * Swizzle around the RSSI calculation as a function, add min/max RSSI values, and calculate RSSI against the noise floor. * And handle the lowest noise floor value - it can't be -127dBm as that will throw things off. Cap it at -100dBm which is a little lower than the thermal noise floor at 20MHz (-98dBm), but it matches IWX_MIN_DBM. Differential Revision: https://reviews.freebsd.org/D53780

linux/linux_common.h: make header self-contained

2026-05-19T04:23:47Z

Sponsored by: The FreeBSD Foundation MFC after: 1 week

linuxkpi: work with numpages > 1 in the set_pages_*() KPIs

2026-05-19T03:22:21Z

These calls are used for buddy pages at least in drm's ttm_pool, which leads to a panic when we invoke lowmem handlers and drm tries to shrink the pool. Cope with numpages > 1 by traversing the contiguous pages and executing the adjustment there, as well, as suggested by markj@. Previous versions have tried to use the corresponding `set_memory_*()` functions, but it is believed that not updating `md.pat_mode` breaks subsequent userspace mappings in ways that may result in things like screen tearing or other artifacts when running i915kms. This stabilized my amdgpu laptop running two VMs, chromium and a concurrent buildworld. Reviewed by: bz, markj Differential Revision: https://reviews.freebsd.org/D57004